{"_id":"575acc2dba4ed70e000ca21a","__v":1,"category":{"_id":"5735cb131f16241700c8a0f7","version":"5735936aafab441700723a53","__v":0,"project":"5735936aafab441700723a50","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-05-13T12:39:47.733Z","from_sync":false,"order":3,"slug":"stage-4-web-site-configuration","title":"Stage 3 - Web site configuration"},"parentDoc":null,"project":"5735936aafab441700723a50","user":"573592b84b0ab120000b7d44","version":{"_id":"5735936aafab441700723a53","__v":12,"project":"5735936aafab441700723a50","createdAt":"2016-05-13T08:42:18.615Z","releaseDate":"2016-05-13T08:42:18.615Z","categories":["5735936aafab441700723a54","5735a32931a73b1700887c94","5735b55beceb872200abbc6c","5735b56eb667601700d3bd6f","5735b9ba4b0ab120000b7dd4","5735b9c94b0ab120000b7dd5","5735cb131f16241700c8a0f7","5735e5c4e4824c3400aa1f21","5735e5d9e4824c3400aa1f23","5735e5f2ec67f6290013ac72","573ecfe0804f901700a9dfc7","573f276c7eeb8b190094ca7d"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":false,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-06-10T14:18:21.698Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"The final step starts the webserver (and, if necessary, restarts it up to 5 times). Usually this will be enough but sometimes you may need to run this script again before your Ensembl instance becomes available at ``http://localhost:$HTTP_PORT/index.html``\n\n```\ncd ~/ei/em\n./reload-ensembl-site.sh ../conf/setup.ini\n```\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Next steps\",\n  \"body\": \"If everything worked up to this point, congratulations you now have your very own Ensembl instance!\\n\\nIf you haven't already, now would be a good time to try [Viewing your Ensembl instance](doc:viewing-your-ensembl-instance), and taking a look at the troubleshooting tips if you're having trouble making your site visible.\\n\\nOnce you've taken a look at the default site, you may want to start customising your Ensembl, either [Using plugins](doc:using-plugins) that already exist or [Creating a plugin](doc:creating-a-plugin) to modify your Ensembl in any way you want.\"\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Configuration options\"\n}\n[/block]\n- [[WEBSITE]](doc:website)\n```\n[WEBSITE]\n    HTTP_PORT = 8080\n```\n  ``HTTP_PORT`` is the port number that the Ensembl website will be hosted on.  If this is set to a value below 1024 (e.g. port 80), the user running this step must have root permissions.","excerpt":"","slug":"step-32-reload-ensembl-website","type":"basic","title":"Step 3.2: Reload Ensembl website"}

Step 3.2: Reload Ensembl website


The final step starts the webserver (and, if necessary, restarts it up to 5 times). Usually this will be enough but sometimes you may need to run this script again before your Ensembl instance becomes available at ``http://localhost:$HTTP_PORT/index.html`` ``` cd ~/ei/em ./reload-ensembl-site.sh ../conf/setup.ini ``` [block:callout] { "type": "success", "title": "Next steps", "body": "If everything worked up to this point, congratulations you now have your very own Ensembl instance!\n\nIf you haven't already, now would be a good time to try [Viewing your Ensembl instance](doc:viewing-your-ensembl-instance), and taking a look at the troubleshooting tips if you're having trouble making your site visible.\n\nOnce you've taken a look at the default site, you may want to start customising your Ensembl, either [Using plugins](doc:using-plugins) that already exist or [Creating a plugin](doc:creating-a-plugin) to modify your Ensembl in any way you want." } [/block] [block:api-header] { "type": "basic", "title": "Configuration options" } [/block] - [[WEBSITE]](doc:website) ``` [WEBSITE] HTTP_PORT = 8080 ``` ``HTTP_PORT`` is the port number that the Ensembl website will be hosted on. If this is set to a value below 1024 (e.g. port 80), the user running this step must have root permissions.