How to set up a retro in 2023 (IIS) (Nitro HTML5) - (Part 1)

EngeldesTodes

Deutsch Techno-Freak WIR SIND EIN
Feb 21, 2011
1,075
77
Having issues with teh WSS sockets any advice it saying configuration error and show on the dev console that says

nitro-renderer-493a6bde.js:103 WebSocket connection to 'wss://ws.vortexhotel.co.uk:2096/' failed: any idea or help please
 

Cav

New Member
Jul 28, 2024
7
0
Thanks for the tutorial. I have a question before I start to work on this. Is it absolutely necessary to do this on a vps? Or can I do this on a Hyper-V host with server 2016/2019 in my LAN? Because I just need this to work over LAN so others on the same network can join. The IP address used will just be a 192.168.x.x address.

Thanks.
 

Joe

Well-Known Member
Jun 10, 2012
4,172
1,955
Thanks for the tutorial. I have a question before I start to work on this. Is it absolutely necessary to do this on a vps? Or can I do this on a Hyper-V host with server 2016/2019 in my LAN? Because I just need this to work over LAN so others on the same network can join. The IP address used will just be a 192.168.x.x address.

Thanks.
You can, but for the sake of a cheap vps ( ) you might as well just get it setup on a VPS, you can follow the tutorial then.
 

Habdream

New Member
Nov 10, 2015
4
4
Restart the vps and try again, I noticed this as well, make sure Java is installed as well.
You must be registered for see images attach


It did not help :(

EDIT:

Took an older version of DBeaver and it works :)
 
Last edited:

kokomegz

New Member
Oct 16, 2024
10
1
Hey boss. I'm stuck on DBeaver right now. It keeps showing an error log, simply will not open the software at all. You ever run into this issue? I updated Java, reinstalled DBeaver, etc....
 

Dark11

New Member
May 4, 2014
15
1
how to fix C:\inetpub\wwwroot>git clone
fatal: could not create work tree dir 'atomcms': Permission denied
 

WJJ

New Member
Jun 26, 2024
1
0
Just wanted to chime in to (hopefully) save anyone reading this some time. This entire three part tutorial is very well written and I am thankful to the OP for taking the time to post it. However, it simply does not work anymore. So if you're planning on spending a few hours going through the steps, I'd save your time.

If you're proficient in the technical aspects (i.e. Laravel, Node, Composer etc.) then you may be able to troubleshoot your way out of the errors, but if you're someone who just wants to set up and play, you'll probably find you're quickly out of your depth and you'll waste a weekend. There's also next to no support/documentation for AtomCMS outside of the Github Wiki which directs you to this three part guide. Likewise, there is a lack of documentation for Nitro and Morningstar. Unless its hidden away on some Discord server somewhere (I know I'm old, but I f*** Discord. This type of documentation/discussion used to be on open forums like this one, and now its all hidden across 10 random Discord servers!).

Before someone accuses me of not being able to follow instructions, I have completed this tutorial from start to finish twice to ensure I hadn't made a stupid mistake. The issues you will run into are as follows:

  • The listed PHP.ini modules are no longer correct, and now require both pdo_sqlite and zip (both easy to fix/enable)
  • Composer complains that the lock file doesn't have a compatible set of packages. This can be fixed by running "composer update --with-all-dependencies" but that could break other things, I wouldn't know.
  • The tutorial doesn't tell you to run "php artisan migrate --seed" which means if you manage to get through all the errors, you wont have the right tables in the db and you wont be able to even get to the installer (you'll get errors about missing tables).
  • There's something wrong with the Vite config in the atom theme that throws an error when you try to go to the installer "Unable to locate file in Vite manifest: resources/css/app.css.". I did manage to get past this error on my first install (cant remember how) and I got to the installer, but once this was done the images were all linked to the wrong location. No idea how I'd even troubleshoot this without having lots of knowledge of Laravel and Vite.
  • There's something confusing with the way it requires a static.domain and nitro.domain subdomains set up, which isn't covered in the guide and I couldn't get the nitro client to work at all (I am not sure if this is due to the instructions for building nitro being out of date, or if I misunderstood, but either way, unless you've got knowledge of how nitro works, you'll be stuck).

So, in summary, unless you've got a lot of background knowledge (in which case, you'd probably not be following this guide in the first place), you wont be able to get anywhere and I'd recommend not bothering.

I am sure from a technical standpoint this CMS is much better, more secure and more robust than the CMS' we used to have in the "old days". However, I cant help but miss being able to simply copy/paste some php files onto a webserver and set up the database credentials... you didn't need a computer science degree and 5 years experience in web frameworks, dependency managers and runtimes back then! Just to be clear, this isn't a complaint about the hard work that the developers have gone to, or to ignore the fact that they are releasing this for free. I really appreciate their efforts. It just seems that the days of being a technically minded teenager and being able to set up a working retro in an afternoon seem to be long gone. :(
 

Users who are viewing this thread

Top