Skip to content
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

Edit does not preserve special variables #326

Open
ryanlelek opened this issue Sep 27, 2020 · 0 comments
Open

Edit does not preserve special variables #326

ryanlelek opened this issue Sep 27, 2020 · 0 comments
Labels
bug Issue with Existing Functionality priority Important ready Ready for Work to Start
Milestone

Comments

@ryanlelek
Copy link
Owner

ryanlelek commented Sep 27, 2020

Issue with editing

production-notes.md

When opening and saving the file, there are changes worth noting.
Marking this down so we have a record

Note:

  • the %base_url% is removed
  • the comments/metadata have changed (at top)

Before:

/*
Title: Production Notes
Sort: 3
*/

When running a live site you'll want to set the `PORT` env variable to `80` so you don't need to add `:3000` to the URL.
This requires root privileges and is not recommended.

Instead it is preferred to use a reverse proxy for security reasons.
Heroku and other services handle this aspect for you, but you can implement your own reverse proxy with Nginx or Apache.
**See [Related Projects](%base_url%/related-projects) for deployment scripts to use on your own servers**

You can change the port anytime by setting the environment variable in your shell's profile, or running in-line as below:
`$ PORT=1234 npm start`

After:

---
Title: Production Notes
Sort: 3
---
When running a live site you'll want to set the `PORT` env variable to `80` so you don't need to add `:3000` to the URL.
This requires root privileges and is not recommended.

Instead it is preferred to use a reverse proxy for security reasons.
Heroku and other services handle this aspect for you, but you can implement your own reverse proxy with Nginx or Apache.
**See [Related Projects](/related-projects) for deployment scripts to use on your own servers**

You can change the port anytime by setting the environment variable in your shell's profile, or running in-line as below:
`$ PORT=1234 npm start`
@ryanlelek ryanlelek added the bug Issue with Existing Functionality label May 10, 2021
@ryanlelek ryanlelek added the ready Ready for Work to Start label Aug 12, 2022
@ryanlelek ryanlelek added this to the v0.18.x milestone Feb 21, 2024
@ryanlelek ryanlelek added the priority Important label Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue with Existing Functionality priority Important ready Ready for Work to Start
Projects
None yet
Development

No branches or pull requests

1 participant