website/README.md

41 lines
524 B
Markdown
Raw Normal View History

2023-01-21 18:06:10 +00:00
# [distrust.co](https://distrust.co)
Web page source.
## Instructions
2023-01-24 20:51:59 +00:00
0. If the repo was not cloned with submodules:
```shell
$ git submodule update --init --recursive
```
Add Dockerized workflow Squashed commit of the following: commit 7c043fea5e7fe2aa431af325f0148d1005c1154e Author: shane <shane@distrust.co> Date: Tue Jan 24 10:06:23 2023 -0600 Change capitalization of makefile to Makefile commit 47c85805d9c28b98063fa87dbff746f5e2fad703 Author: shane <shane@distrust.co> Date: Tue Jan 24 09:55:23 2023 -0600 Re-remove shell scripts to be run by Makefile `$PWD`, it turns out, does not resolve in Makefiles. Perhaps this is because it is not strictly running `bash` from a `source`d shell environment. When instead computing the value with `$(shell pwd)`, the volume mounts are successful and the operations perform as-expected. commit dc5952bef488010d4dd9e7b44c688a4033b5f0b2 Author: shane <shane@distrust.co> Date: Tue Jan 24 09:42:06 2023 -0600 Re-add shell scripts to run from Makefile If the Makefile executes the same commands, they do not effectively do the right thing. The files for the _site directory do not get created and the server only resolves to an empty site directory. Nothing was changed about the commands. This just seems to be something about `make`'s permissions. commit 2c98664076c071082d3a1807b40a322a8ecab174 Author: shane <shane@distrust.co> Date: Tue Jan 24 09:00:39 2023 -0600 Remove redundancies from Makefile process - Move contents of build.sh to `build:` target - Move contents of serve.sh to `serve:` target commit 09d9964453425245025560e46a5b25e1c8d3c746 Author: shane <shane@distrust.co> Date: Tue Jan 24 08:59:15 2023 -0600 Re-add Gemfile.lock - This one was produced with the most recent Gemfile version commit 13768779681292b48a3a23a65824bca466be1611 Author: shane <shane@distrust.co> Date: Mon Jan 23 21:22:42 2023 -0600 Add Dockerized workflow
2023-01-24 20:51:59 +00:00
1. Install `make`.
2. Install `docker`
3. Build (export) site to `_site` directory:
2023-01-21 18:06:10 +00:00
```shell
Add Dockerized workflow Squashed commit of the following: commit 7c043fea5e7fe2aa431af325f0148d1005c1154e Author: shane <shane@distrust.co> Date: Tue Jan 24 10:06:23 2023 -0600 Change capitalization of makefile to Makefile commit 47c85805d9c28b98063fa87dbff746f5e2fad703 Author: shane <shane@distrust.co> Date: Tue Jan 24 09:55:23 2023 -0600 Re-remove shell scripts to be run by Makefile `$PWD`, it turns out, does not resolve in Makefiles. Perhaps this is because it is not strictly running `bash` from a `source`d shell environment. When instead computing the value with `$(shell pwd)`, the volume mounts are successful and the operations perform as-expected. commit dc5952bef488010d4dd9e7b44c688a4033b5f0b2 Author: shane <shane@distrust.co> Date: Tue Jan 24 09:42:06 2023 -0600 Re-add shell scripts to run from Makefile If the Makefile executes the same commands, they do not effectively do the right thing. The files for the _site directory do not get created and the server only resolves to an empty site directory. Nothing was changed about the commands. This just seems to be something about `make`'s permissions. commit 2c98664076c071082d3a1807b40a322a8ecab174 Author: shane <shane@distrust.co> Date: Tue Jan 24 09:00:39 2023 -0600 Remove redundancies from Makefile process - Move contents of build.sh to `build:` target - Move contents of serve.sh to `serve:` target commit 09d9964453425245025560e46a5b25e1c8d3c746 Author: shane <shane@distrust.co> Date: Tue Jan 24 08:59:15 2023 -0600 Re-add Gemfile.lock - This one was produced with the most recent Gemfile version commit 13768779681292b48a3a23a65824bca466be1611 Author: shane <shane@distrust.co> Date: Mon Jan 23 21:22:42 2023 -0600 Add Dockerized workflow
2023-01-24 20:51:59 +00:00
$ make build
```
Add Dockerized workflow Squashed commit of the following: commit 7c043fea5e7fe2aa431af325f0148d1005c1154e Author: shane <shane@distrust.co> Date: Tue Jan 24 10:06:23 2023 -0600 Change capitalization of makefile to Makefile commit 47c85805d9c28b98063fa87dbff746f5e2fad703 Author: shane <shane@distrust.co> Date: Tue Jan 24 09:55:23 2023 -0600 Re-remove shell scripts to be run by Makefile `$PWD`, it turns out, does not resolve in Makefiles. Perhaps this is because it is not strictly running `bash` from a `source`d shell environment. When instead computing the value with `$(shell pwd)`, the volume mounts are successful and the operations perform as-expected. commit dc5952bef488010d4dd9e7b44c688a4033b5f0b2 Author: shane <shane@distrust.co> Date: Tue Jan 24 09:42:06 2023 -0600 Re-add shell scripts to run from Makefile If the Makefile executes the same commands, they do not effectively do the right thing. The files for the _site directory do not get created and the server only resolves to an empty site directory. Nothing was changed about the commands. This just seems to be something about `make`'s permissions. commit 2c98664076c071082d3a1807b40a322a8ecab174 Author: shane <shane@distrust.co> Date: Tue Jan 24 09:00:39 2023 -0600 Remove redundancies from Makefile process - Move contents of build.sh to `build:` target - Move contents of serve.sh to `serve:` target commit 09d9964453425245025560e46a5b25e1c8d3c746 Author: shane <shane@distrust.co> Date: Tue Jan 24 08:59:15 2023 -0600 Re-add Gemfile.lock - This one was produced with the most recent Gemfile version commit 13768779681292b48a3a23a65824bca466be1611 Author: shane <shane@distrust.co> Date: Mon Jan 23 21:22:42 2023 -0600 Add Dockerized workflow
2023-01-24 20:51:59 +00:00
4. Serve site at `0.0.0.0:4000`:
Add Dockerized workflow Squashed commit of the following: commit 7c043fea5e7fe2aa431af325f0148d1005c1154e Author: shane <shane@distrust.co> Date: Tue Jan 24 10:06:23 2023 -0600 Change capitalization of makefile to Makefile commit 47c85805d9c28b98063fa87dbff746f5e2fad703 Author: shane <shane@distrust.co> Date: Tue Jan 24 09:55:23 2023 -0600 Re-remove shell scripts to be run by Makefile `$PWD`, it turns out, does not resolve in Makefiles. Perhaps this is because it is not strictly running `bash` from a `source`d shell environment. When instead computing the value with `$(shell pwd)`, the volume mounts are successful and the operations perform as-expected. commit dc5952bef488010d4dd9e7b44c688a4033b5f0b2 Author: shane <shane@distrust.co> Date: Tue Jan 24 09:42:06 2023 -0600 Re-add shell scripts to run from Makefile If the Makefile executes the same commands, they do not effectively do the right thing. The files for the _site directory do not get created and the server only resolves to an empty site directory. Nothing was changed about the commands. This just seems to be something about `make`'s permissions. commit 2c98664076c071082d3a1807b40a322a8ecab174 Author: shane <shane@distrust.co> Date: Tue Jan 24 09:00:39 2023 -0600 Remove redundancies from Makefile process - Move contents of build.sh to `build:` target - Move contents of serve.sh to `serve:` target commit 09d9964453425245025560e46a5b25e1c8d3c746 Author: shane <shane@distrust.co> Date: Tue Jan 24 08:59:15 2023 -0600 Re-add Gemfile.lock - This one was produced with the most recent Gemfile version commit 13768779681292b48a3a23a65824bca466be1611 Author: shane <shane@distrust.co> Date: Mon Jan 23 21:22:42 2023 -0600 Add Dockerized workflow
2023-01-24 20:51:59 +00:00
```shell
$ make serve
2023-01-21 18:06:10 +00:00
```
### Generate Static Files
1. Output static files in `_site` directory:
```shell
$ make _site
```
### Cleanup
1. Remove all build artifacts:
```shell
$ make fullclean
```