New to READYNAS Webserver

---

Nix2021 wrote:

Not sure if this is the correct "Board" or even forum.....

 

I have had my READYNAS for several years and just upgraded it to 4x10TB Drives at RAID 5. Seems like a good time to try and use the system as a webserver.

 

I am used to apache, php, etc....

 

I particular I want to use javascript, and css. Is this difficult to do with the READYNAS w/o sshing in and modifying the underlying OS via CLI.

---

I haven't done this myself, so I don't know the limits. But the admin web UI does use css and json is installed.

There is some information here on how to set up the NAS to do this: https://kb.netgear.com/24829/ReadyNAS-OS-6-Create-a-personal-webserver

---

Nix2021 wrote:

Seems like a good time to try and use the system as a webserver. I am used to apache, php, etc....

The webserver used on ReadyNAS is Apache. PHP is also installed.

---

Nix2021 wrote:

I am used to apache, php, etc....

---

I'm running my website from a ReadyNAS for several years now. It uses PHP, JavaScript and CSS. So using this in your website shouldn't be a problem.

---

Nix2021 wrote:

I particular I want to use javascript, and css. Is this difficult to do with the READYNAS w/o sshing in and modifying the underlying OS via CLI.

---

The page suggested by StephenB looks like a good starting point. It explains how you can create a WebSite share (without using the CLI), that you can then access from a PC via the network. You could manually copy your webpages to this Web Share, or connect a web development tool to it. This should be sufficient for you if you only wish to use JavaScript and CSS.

If you want to expose a (dynamic) website to the Internet, there are few things to consider and you may have to do some work on the CLI.

1. HTTPS. Self-signed certificates are not accepted by most modern browsers. To prevent all kinds of warnings you need a certifcate issued by a Certificate Authority. You may need to setup an automated process to periodically renew these certifcates. And change the Apache configuration to include HTTPS.
2. If you want to use a dynamic website that uses a database, you can use e.g. PHP and MySQL. Note that the default location of the MySQL data files has limited disk space. You want to make sure the rootfs doesn't fill up quickly as your database gets bigger. To prevent this you need to move MySQL data files out of the root partition and create symbolic links to the new location.
3. If you want to expirement with ReadyNAS OS you can set it up as a VM on your PC first. This will enable you to change settings and make mistakes, without accidently messing up your installation on your physical ReadyNAS.
4. For security reason you may want to prevent the ReadyNAS OS Admin page from being exposed to the Internet.

These related pages might be of interest to you:

https://stackoverflow.com/questions/21415181/can-i-stop-the-this-website-does-not-supply-identity-information-message 

https://community.netgear.com/t5/ReadyNAS-Storage-Apps-Current/How-to-run-Koken-on-https/m-p/1095537#M5084 

https://fotografeer.nl/index.php?/categories/blog/essays/koken-cms-on-https/ 

https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/rootfs-increases-by-5-to-10-during-USB-backup/m-p/960272/highlight/true#M159806 
https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/WordPress-on-Docker-on-ReadyNAS-OS-VM/m-p/1681325 
https://fotografeer.nl/index.php?/categories/blog/essays/wordpress-on-docker-on-readynas-os-vm/