-
Notifications
You must be signed in to change notification settings - Fork 2
Add systemd and guide #2
base: master
Are you sure you want to change the base?
Conversation
README.md
Outdated
| @@ -0,0 +1,71 @@ | |||
| # Preface | |||
|
|
|||
| This assume you have installed codius, if you havent please do so first. If you are using the community installer, this install guide will be added soon on that script. | |||
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.
I wouldn't make any promises regarding the Community Installer. We don't have a direct relationship with maintenance of the community installer, so I think it's best not to imply that we have that kind say in its development cycle, and vice versa.
| add_header X-XSS-Protection '1; mode=block'; | ||
|
|
||
| location / { | ||
| allow 127.0.0.1; |
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.
I recommend adding a sample YOUR_TRUSTED_IP or something of the like here, to illustrate where in the config it should go.
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.
updated
| # How to install codiusd-gui: | ||
|
|
||
| This will install the GUI and once sucessfully started it will run on 127.0.0.1 on port 3300. You can SSH | ||
| redirect in, or you can add an NGinx config |
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.
I'd suggest adding the SSH redirect/tunnel method as well. It's arguably more simple than creating a new nginx config.
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.
updated
| } | ||
|
|
||
| server { | ||
| listen 444 ssl; |
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.
It would be beneficial to tell the reader that nginx will start listening on port 444, which will have to be explicitly included in the url (e.g. https://codius.example.com:443) to be reached unlike 443 and 80, which are implicitly routed to for HTTPS and HTTP requests.
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.
updated
| @@ -0,0 +1,14 @@ | |||
| [Unit] | |||
| Description=Codiusd GUI | |||
| After=network.target nss-lookup.target codiusd | |||
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.
The nss-lookup.target argument should be codiusd-gui instead of codiusd
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.
i dont think so? it just means it will start after networking and codiusd have been started, which in the order of things makes sense no?
|
I have updated most parts now, it works for me as expected. |
such fun we have with codius, sharing it back