-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✏️ Spacing changes for docs project #289
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
williln
commented
Aug 6, 2024
Comment on lines
-48
to
+63
```sh | ||
# to start the containers detached in the background | ||
just docker start | ||
# to start the containers in the foreground with the logs continuously streaming in stdout | ||
just docker up | ||
``` | ||
To start the containers in the background: | ||
|
||
After starting, you should be able to access the development server at [http://localhost:8000](http://localhost:8000). | ||
```sh | ||
just docker start | ||
``` | ||
|
||
By default, the development server will run on port 8000. If you need to change the port, you can do so by setting the `DJANGO_PORT` environment variable in the `.env` file and then restarting the development server. | ||
To start the containers in the foreground with the logs continuously streaming in stdout | ||
|
||
```sh | ||
just docker up | ||
``` | ||
|
||
After starting, you should be able to access the development server at [http://localhost:8000](http://localhost:8000). | ||
|
||
By default, the development server will run on port 8000. If you need to change the port, you can do so by setting the `DJANGO_PORT` environment variable in the `.env` file and then restarting the development server. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is all the same, it's just split up a little bit for formatting purposes. (I was having trouble getting the list, code, and paragraph to render appropriately in mkdocs, and splitting it up seemed to help.)
joshuadavidthomas
approved these changes
Aug 6, 2024
This was referenced Aug 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The editorconfig is already set to 4 spaces, so this just brings the README in line with that. This benefits mkdocs over in https://github.com/westerveltco/central-docs/