The latest articles on DEV Community by Vern Martin (@wearahelmet). https://dev.to/wearahelmet https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F310392%2F45054740-5239-466e-8ab2-9a5ad32c5f93.gif https://dev.to/wearahelmet en Vern Martin Sat, 11 Jan 2020 14:30:03 +0000 https://dev.to/wearahelmet/deploying-svelte-app-to-iis-1kia https://dev.to/wearahelmet/deploying-svelte-app-to-iis-1kia <p>Nothing fancy here -- just the absolutely bare minimum setup.</p> <p>I did not find any deployment guidance on the web specifically for IIS. I know just enough about IIS to get this working, so feel free to suggest a better way. Here is what I had to do to get the app working.</p> <ul> <li>modify the public/index.html file (came from the Svelte template) to remove the leading / from the public/index.html for style sheets and bundle, so href='/global.css' became href='global.css'</li> <li>do this for the favicon as well</li> <li>build the build command: npm run build</li> <li>copy the public directory to some target application directory on the target server</li> <li>add an "app" to the default site in IIS on the target server, give it a name, let's say it's "blackbird," and when it asks for the directory path, set it to "public" in the application directory</li> <li>the app url then is: <a href="http://target_server_name/blackbird">http://target_server_name/blackbird</a> </li> </ul> <p>The main takeaway was to fix the paths in index.html. I could see in the console the errors that the app was not finding these files and clearly the app was not starting up.</p> <p>This does <strong>NOT</strong> seem to break anything during development when I run "npm run dev"</p> iis svetle deployment