Conversation

Notices

1. Embed this notice
   naskya::dev (dev@post.naskya.net)'s status on Friday, 02-Jun-2023 06:05:12 JST naskya::dev

   • pere פרא

   @pere@micro.towards.vision Hello 😀
   I am interested in Vervis and would like to host it on my server, but to be honest, I am unsure how to deploy the app properly. Could you please share the deployment script or tell me how to deploy it manually? I am not in a hurry and would appreciate if you can answer me when you have time.
   I'm using Ubuntu Server 22.04 LTS.
   
   Thank you so much for creating great software 😆

   • Embed this notice
     naskya::dev (dev@post.naskya.net)'s status on Monday, 05-Jun-2023 16:41:58 JST naskya::dev

     in reply to

     • pere פרא

     @pere@micro.towards.vision Thank you for your kind reply. Yes, I understand it's in a pre-alpha stage, and I still want to deploy manually!

   • Embed this notice
     pere פרא (pere@micro.towards.vision)'s status on Monday, 05-Jun-2023 16:42:04 JST pere פרא

     in reply to

     • Forgejo

     Hi @dev ! I'm excited about people wanting to host Vervis ^_^

     Vervis is in a pre-alpha stage, not safe to use in "production" yet, and there's no Docker/Yunohost/etc. setup yet. Do you still wish to deploy it manually? If yes, I'm happy to tell you how.

     Otherwise my recommendation for now is to host your code using @forgejo .

     naskya::dev likes this.
   • Embed this notice
     naskya::dev (dev@post.naskya.net)'s status on Wednesday, 21-Jun-2023 08:14:31 JST naskya::dev

     in reply to

     • pere פרא

     @pere@micro.towards.vision Thanks a lot! Also, please don't worry if you can't reply immediately! I know you are working on amazing stuff :meow_heart_hug:
     Currently, I've managed to run Vervis locally (just an FYI, I had to install pkg-config and libcurl4-openssl-dev, which I think isn't mentioned in INSTALL.md, but that was not a big deal), but I have trouble with deploying it on my server; I can't access it on https://instance.tld (image #1), and I have to type http://instance.tld:3000 instead (image #2).
     It may be more of a web server management thing than something specific to Vervis (honestly, I'm a newbie in server management), so I'm sorry if this is due to my misconfiguration.
     I'm currently using nginx to forward ports, but it's okay to switch to other methods, so please tell me if you recommend any other way.
     
     I have /etc/nginx/sites-available/vervis like this (please check this on remote if the code block is hard to see on Mastodon)upstream vervis { server 127.0.0.1:3000 max_fails=5 fail_timeout=60s; } server { server_name code.naskya.net; listen 80; listen [::]:80; listen 443 ssl http2; listen [::]:443 ssl http2; ssl_certificate /path/to/cert ssl_certificate_key /path/to/cert_key proxy_http_version 1.1; proxy_set_header Host $http_host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; location / { proxy_pass http://vervis; } }
     and config/settings.yml like this:host: "_env:HOST:*4" http-port: "_env:PORT:3000" ip-from-header: "_env:IP_FROM_HEADER:false" instance-host: "_env:INSTANCE_HOST:code.naskya.net" # and so on...
     Big thanks in advance.

   • Embed this notice
     pere פרא (pere@micro.towards.vision)'s status on Wednesday, 21-Jun-2023 08:14:37 JST pere פרא

     in reply to

     @dev Out of the various key/config files, the ones I keep on my laptop are the ones I generated manually:

     - config/settings.yml
     - SSH public & private key (in config/ as well)

     The rest of the keys are generated by Vervis and kept on the server (but you may want to have a backup of them somewhere just in case)

     Does this help? Let me know any questions :)

   • Embed this notice
     pere פרא (pere@micro.towards.vision)'s status on Wednesday, 21-Jun-2023 08:14:43 JST pere פרא

     in reply to

     Hi @dev ! I seem to be way more busy that I'd like lately, but I do want to give you some info, even if it's the complete picture I wish I had.

     Basically I build Vervis on my laptop:

     https://paste.towards.vision/?afe116b1a5ff8ab2#Y1ftS5hegTxdh7cNgg9Qw9qy2Q5GRKP92uVZJVw2XGF

     Then upload using rsync to some folder on the server:

     https://paste.towards.vision/?834163dad4998fb8#HukMCVoYMKDw15yLxUPJN29MZeUtddHnYSvxHH3HrJBu

     I then have a script that runs in cron, as root, that (if Vervis crashed/stopped) copies those files to the liv dir (which I have under /var/lib) and launches Vervis

     https://paste.towards.vision/?0661540f6ad84d3a#HL7yDN8fcLnzWL3hXJRryqjVU3gM41kJKsiFitf7kW21