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

Object

?
Nov 10, 2017
429
350
Welcome to the part 2 of the "how to set up a retro with IIS" series! In this part we'll make a A LOT of progress towards making your new hotel playable 🚀

What will we cover in part 2:
Atom CMS setup
Atom HK setup
Volta (multi-node installations)
Nitro Converter setup

We'll need multiple versions of Node in-order to setup everything needed to play your new hotel, so to do that, we'll install a tool called "Volta" - Volta is a tool that lets us install & manage multiple versions of node hassle-free ✨

Head to and click on the " " - Go through the installation process. Once volta has been installed re-open your CMD (command prompt) and enter:
Code:
volta install [email protected]
And
volta install node

Install yarn
Code:
volta install yarn@latest

It's finally time to set up Atom CMS! this is the part where things start to get a little exciting, as we will get to see our website start functioning.

The first step of our road to set up Atom CMS will be to enable the PHP extensions required by Atom CMS to function properly, to do that head to C:\Program Files\PHP and scroll down until you find a file named "php" which is of file type "INI"
You must be registered for see images attach


Open the file in your preferred editor (Mine will be Visual Studio Code)

Find the extensions list (You can find the list quickly by searching for "Dynamic Extensions") Once you've found the list, replace it with the extension list below.

Code:
;extension=bz2
extension=curl
;extension=ffi
;extension=ftp
extension=fileinfo
extension=gd
;extension=gettext
;extension=gmp
;extension=intl
;extension=imap
;extension=ldap
extension=mbstring
;extension=exif      ; Must be after mbstring as it depends on it
;extension=mysqli
;extension=oci8_12c  ; Use with Oracle Database 12c Instant Client
;extension=oci8_19  ; Use with Oracle Database 19 Instant Client
;extension=odbc
extension=openssl
;extension=pdo_firebird
extension=pdo_mysql
;extension=pdo_oci
;extension=pdo_odbc
;extension=pdo_pgsql
;extension=pdo_sqlite
;extension=pgsql
;extension=shmop
; The MIBS data available in the PHP distribution must be installed.
; See https://www.php.net/manual/en/snmp.installation.php
;extension=snmp
;extension=soap
extension=sockets
;extension=sodium
;extension=sqlite3
;extension=tidy
;extension=xsl

The next step
* If you have the URL Rewrite extension installed already, skip to the "Install Atom CMS" step below.

If you didn't install the URL Rewrite extension in part one, you'll have to install it now - . Simply click "Install this extension" and go through the setup process

Install Atom CMS:
Start by heading into your Atom CMS folder by opening command prompt (CMD) and enter
Code:
cd C:/inetpub/wwwroot/atomcms

Next up enter the following your CMD
Code:
copy .env.example .env

* Leave your terminal open and continue to "Connect Atom CMS to your database & then Dependencies installation" below.

Connect Atom CMS to your database:
To make Atom CMS able to communicate with our database, we'll have to set the correct credentials, to do that open the .env file that is now located in the root of the Atom CMS folder, and fill in your database credentials as well as the correct database name - The variables you'll have to edit can be found below:

DB_DATABASE=your-database-name
DB_USERNAME=root
DB_PASSWORD=your-database-password

Dependencies installation:
Atom CMS relies on multiple different dependencies which we will have to install - To install those dependencies write the following commands
Code:
composer install && npm i && npm run build:atom

This will install all the required dependencies & compile the necessary assets for you.

You must be registered for see images attach

For Atom CMS to function we'll also have to generate an application key - luckily this is a simple process as well! All you have to do is to enter the following command in your CMD (command prompt)
Code:
php artisan key:generate

Connect Atom CMS with IIS:
The time has come! We will now be connecting Atom CMS with IIS to make us able to browse our newly setup website 🚀

Step one:
Open up your Internet Information Services application and expand the section just below "Start Page"

You must be registered for see images attach


Expand the "sites" section and right-click on the "Default website" and then "remove".

You will then have to add a new site to IIS and to do that, right-click yet again on the "Sites" and click "Add Website..."
You must be registered for see images attach


In the "Site name:" field enter whatever name you find appropriate. In my case, I will just enter my domain name.

Next click the 3 dots next to the "Physical path:" field and browse into the "public" folder inside the "atomcms" folder. Once you have clicked on the "public" folder, click the "OK" button.

Once you have done all of the above your "Add website" popup should look like this:
You must be registered for see images attach


If that's the case simply click "OK".

Next up we'll have to give full permission to the "atomcms" folder. To achieve this, browse yourself into the "C:\inetpub\wwwroot" folder and right-click on the "atomcms" folder select "Properties" then click the "Security" tab and click on "Edit..." and then "Add..." - A pop up should appear looking like the image below.

You must be registered for see images attach


Enter "IIS_IUSRS" and then "OK". Click on "Add..." once more and add "IUSR" and then "OK".

Once both the "users" have been added, find both of them in the list and click them individually, once they have been selected toggle the "Full control" and then click "Apply" (Don't forget to do this on both the added users).

Check the images below, if you're unsure if you did it correctly✨
You must be registered for see images attach

You must be registered for see images attach

You must be registered for see images attach

Once Atom CMS has been linked through IIS, you will be able to visit it through your domain name. The first time you visit it, you'll be prompted with an installation screen, which required you to paste in an installation code. This code can be found inside your database manager (DBeaver) within the table "website_installation" copy this code and paste it in, then go through the installation steps.

Important: Once you've finished the installation steps, open your .env files within your preferred editor once more, and set the APP_ENV to:
Code:
APP_ENV=production
and the APP_DEBUG to:
Code:
APP_DEBUG=false

Before we can enter our hotel, we'll need to set up our emulator and to do that, the first thing we need to do is to install Java.

To install Java all you have to do is to download it -

Once Java has been downloaded, go through the setup process, by leaving everything to their default preset (Simply click "Install" and let Java install itself).

Java has been installed:
When Java has been installed, it should look like the image below:
You must be registered for see images attach

Start by heading into your File explorer and navigate int othe following: "C:/ -> inetpub -> wwwroot -> atomcms -> public -> client" Here you'll find yourself with a folder called "emulator" simply drag it out to your desktop.

Open the "emulator" folder now located on your desktop and then edit the database credentials inside the config.ini file, so that they match the ones you made when setting up MariaDB - If you don't remember your credentials, simply open the .env file located in the root folder for Atom CMS and take them from there.

Once you've edited the config.ini so that the database credential matches you can safely save and close the config.ini file again.

Lastly click on the "start.bat" file so that your emulator fully boots up, once it's booted up, you can simply close it it back down.

There you go! Your emulator should now run smoothly for the future.

You're doing an amazing job so far 🎉 In the next part we will go through the process of setting up:
Nitro v2 & connect it's assets (latest as of July 2023)

To learn how to do all of the above, head to part 3 of this series, which will be the last and final part🥳


Did I miss anything?
Please let me know if I missed anything, as the guide contains a lot of information.
 

Attachments

  • 1638741023539.png
    1638741023539.png
    17.8 KB · Views: 1,711
  • 1638741067299.png
    1638741067299.png
    24.4 KB · Views: 635
  • 1638741088267.png
    1638741088267.png
    23.5 KB · Views: 1,500
  • 1639000812504.png
    1639000812504.png
    70.4 KB · Views: 1,478
  • 1639002626969.png
    1639002626969.png
    73.5 KB · Views: 2,724
  • 1661006116877.png
    1661006116877.png
    11.9 KB · Views: 396
  • 1661006315950.png
    1661006315950.png
    17.8 KB · Views: 368
  • 1661013442080.png
    1661013442080.png
    39.9 KB · Views: 1,738
  • 1661015791092.png
    1661015791092.png
    9.3 KB · Views: 1,645
  • 1665606050423.png
    1665606050423.png
    11.7 KB · Views: 400
Last edited:

TheRealJayhorn

New Member
Dec 7, 2021
5
0
I'd need more info than that, is it IIS or cosmic that throws the error. eventually a screenshot will do
Yeah let me just log into the box real quick, it's when I try to load the website
9041870e6d85c7fb3a9765356ec9c9fd.png

 

Object

?
Nov 10, 2017
429
350
Yeah let me just log into the box real quick, it's when I try to load the website
9041870e6d85c7fb3a9765356ec9c9fd.png

Your database password seems to be incorrect - Make sure to edit the .env file with the correct credentials (My bad for forgetting to include this part in the thread. I have now corrected it.

"To make Cosmic CMS able to communicate with our database, we'll have to set the correct credentials, and to do that, open the .ENV file located in the root of the Cosmic folder, and fill in your database credentials as well as the correct database name."
 
Last edited:

Object

?
Nov 10, 2017
429
350
Alright, I got that fixed, but when I go to load into the hotel it's just stuck on an endless loading with the login, do you know how to fix that?
Not exactly no. Everything should be covered in the thread (to what I can remember on top of my head), so I feel like if everything has been done without any issues it should be fine. You can try and open dev tool (f12) and go to network and once u login, let me know if it gives u any error
 

TheRealJayhorn

New Member
Dec 7, 2021
5
0
Not exactly no. Everything should be covered in the thread (to what I can remember on top of my head), so I feel like if everything has been done without any issues it should be fine. You can try and open dev tool (f12) and go to network and once u login, let me know if it gives u any error
It's not giving me any errors with dev tool, everythings working fine on the website it's just the client being weird.
0cc7610f58db6039d6fe1a6a5ae3c753.png


It goes to load and restarts.
 

Object

?
Nov 10, 2017
429
350
It's not giving me any errors with dev tool, everythings working fine on the website it's just the client being weird.
0cc7610f58db6039d6fe1a6a5ae3c753.png


It goes to load and restarts.
Oh, the tutorial hasn't been finished yet as it stated at the very beginning of this thread, anything after the cosmic cms setup has yet to be explained. If you're trying to add the client yourself and seem to be stuck. I'd recommend that you head to the help section and ask there :D
Post automatically merged:

The thread has just been updated to contain the process of setting up the nitro converter as well!
 
Last edited:

Jamescool12

Member
Jan 17, 2014
139
13

2 "output.folder": "C:/inetpub/wwwroot/Cosmic/public/client/html5/nitro-assets/",
~
src/Main.ts:3:23 - error TS1005: ';' expected.

3 "flash.client.url": " ",
~
src/Main.ts:4:19 - error TS1005: ';' expected.

4 "gamedata.url": "${flash.client.url}/gamedata",
~
src/Main.ts:5:25 - error TS1005: ';' expected.

5 "furnidata.load.url": "${gamedata.url}/furnidata.xml",
~
src/Main.ts:6:27 - error TS1005: ';' expected.

6 "productdata.load.url": "${gamedata.url}/productdata.txt",
~
src/Main.ts:7:26 - error TS1005: ';' expected.

7 "figuredata.load.url": "${gamedata.url}/figuredata.xml",
~
src/Main.ts:8:25 - error TS1005: ';' expected.

8 "figuremap.load.url": "${gamedata.url}/figuremap.xml",
~
src/Main.ts:9:25 - error TS1005: ';' expected.

9 "effectmap.load.url": "${gamedata.url}/effectmap.xml",
~
src/Main.ts:10:31 - error TS1005: ';' expected.

10 "dynamic.download.pet.url": "${flash.client.url}/gordon/PRODUCTION/%className%.swf",
~
src/Main.ts:11:34 - error TS1005: ';' expected.

11 "dynamic.download.figure.url": "${flash.client.url}/gordon/PRODUCTION/%className%.swf",
~
src/Main.ts:12:34 - error TS1005: ';' expected.

12 "dynamic.download.effect.url": "${flash.client.url}/gordon/PRODUCTION/%className%.swf",
~
src/Main.ts:13:33 - error TS1005: ';' expected.

13 "flash.dynamic.download.url": "${flash.client.url}/dcr/hof_furni",
~
src/Main.ts:14:37 - error TS1005: ';' expected.

14 "dynamic.download.furniture.url": "${flash.dynamic.download.url}/%className%.swf",
~
src/Main.ts:15:29 - error TS1005: ';' expected.

15 "external.variables.url": "${gamedata.url}/external_variables.txt",
~
src/Main.ts:16:25 - error TS1005: ';' expected.

16 "external.texts.url": "${gamedata.url}/external_flash_texts.txt",
~
src/Main.ts:17:21 - error TS1005: ';' expected.

17 "convert.figure": "1",
~
src/Main.ts:18:21 - error TS1005: ';' expected.

18 "convert.effect": "1",
~
src/Main.ts:19:24 - error TS1005: ';' expected.

19 "convert.furniture": "1",
~
src/Main.ts:20:18 - error TS1005: ';' expected.

20 "convert.pet": "1",
~
src/Main.ts:21:29 - error TS1005: ';' expected.

21 "misc.log_download_urls": "0"
~
 

Object

?
Nov 10, 2017
429
350
2 "output.folder": "C:/inetpub/wwwroot/Cosmic/public/client/html5/nitro-assets/",
~
src/Main.ts:3:23 - error TS1005: ';' expected.

3 "flash.client.url": " ",
~
src/Main.ts:4:19 - error TS1005: ';' expected.

4 "gamedata.url": "${flash.client.url}/gamedata",
~
src/Main.ts:5:25 - error TS1005: ';' expected.

5 "furnidata.load.url": "${gamedata.url}/furnidata.xml",
~
src/Main.ts:6:27 - error TS1005: ';' expected.

6 "productdata.load.url": "${gamedata.url}/productdata.txt",
~
src/Main.ts:7:26 - error TS1005: ';' expected.

7 "figuredata.load.url": "${gamedata.url}/figuredata.xml",
~
src/Main.ts:8:25 - error TS1005: ';' expected.

8 "figuremap.load.url": "${gamedata.url}/figuremap.xml",
~
src/Main.ts:9:25 - error TS1005: ';' expected.

9 "effectmap.load.url": "${gamedata.url}/effectmap.xml",
~
src/Main.ts:10:31 - error TS1005: ';' expected.

10 "dynamic.download.pet.url": "${flash.client.url}/gordon/PRODUCTION/%className%.swf",
~
src/Main.ts:11:34 - error TS1005: ';' expected.

11 "dynamic.download.figure.url": "${flash.client.url}/gordon/PRODUCTION/%className%.swf",
~
src/Main.ts:12:34 - error TS1005: ';' expected.

12 "dynamic.download.effect.url": "${flash.client.url}/gordon/PRODUCTION/%className%.swf",
~
src/Main.ts:13:33 - error TS1005: ';' expected.

13 "flash.dynamic.download.url": "${flash.client.url}/dcr/hof_furni",
~
src/Main.ts:14:37 - error TS1005: ';' expected.

14 "dynamic.download.furniture.url": "${flash.dynamic.download.url}/%className%.swf",
~
src/Main.ts:15:29 - error TS1005: ';' expected.

15 "external.variables.url": "${gamedata.url}/external_variables.txt",
~
src/Main.ts:16:25 - error TS1005: ';' expected.

16 "external.texts.url": "${gamedata.url}/external_flash_texts.txt",
~
src/Main.ts:17:21 - error TS1005: ';' expected.

17 "convert.figure": "1",
~
src/Main.ts:18:21 - error TS1005: ';' expected.

18 "convert.effect": "1",
~
src/Main.ts:19:24 - error TS1005: ';' expected.

19 "convert.furniture": "1",
~
src/Main.ts:20:18 - error TS1005: ';' expected.

20 "convert.pet": "1",
~
src/Main.ts:21:29 - error TS1005: ';' expected.

21 "misc.log_download_urls": "0"
~
?
 

Object

?
Nov 10, 2017
429
350
So i am trying to converting the assets but i keep getting error
How does your IIS site binding look like? However you can also just change localhost in the config to your domain, and it should be all good to go
 

kimzyyyy

New Member
Mar 3, 2020
15
5
How does your IIS site binding look like? However you can also just change localhost in the config to your domain, and it should be all good to go
7afd7c19c86f32290f96e8c36c01add2.png


 

Shayn

New Member
Mar 17, 2019
2
0
Hello i have a problem before the start of the CMS :
You have the solution ?
 

Users who are viewing this thread

Top