Removing Web "Site" publishing to

Posted by Titas Norkunas on August 20, 2012 10:56:00 AM

We are deprecating a feature in our repositories which automatically publishes the current version of of a repository to <myname>  You will find this feature under the "Sites" submenu option in your repostory tool.  It's a very convenient feature, but over all time, only about 1000 people have used it.  So, we will remove it and replace it with more popular build options.  We will remove it after September 15th.

We apologize if we are causing problems for any users of this feature.  If you have concerns about this plan, please email, and I will respond personally.

There are more popular options for publishing your repository content as a Web site.

1) "View as Web Page" in the code browser

If you are sharing your site with colleagues and clients, you can go to the Web browser, navigate to a Web page that you want to view, and select the "View as Web Page" button on the top.  This will render the file as a Web page in your browser. If you created the Web site with relative links, you can navigate your site in this view.  It's actually exactly the same as the site view on <myname>, which uses the same rendering mechanism, except that it applies permissions. You can send the "View as Web page" URL link to anyone with permission to view your repository.

2) FTP publishing to your normal Web server

We offer an FTP tool that is quite popular. This tool uses FTP to push the current version of the repository, or any historical version, to a Web server. Most commercial Web server hosts accept FTP.

3) Git publishing to free cloud services, including Heroku

You can get a small free cloud server from Amazon, or a cloud service with ability to run applications from Heroku.  Here are some instructions and links to publish on Heroku in less than half an hour. Using windows and need to set up git? Here is a handy guide.

1. Follow steps 1-3 here. Instead of diving into step 4 (which you might as well do) follow the instructions below.
2. Grab our Free git space here and clone it locally
3. Create an empty index.php and .htaccess files in the repository and add "php_flag engine off" line to .htaccess file.

touch index.php
echo 'php_flag engine off' > .htaccess

4. Move your static content to the repository and make a commit

git add .
git commit -m "First commit"

5. push to assembla, run heroku create, push to heroku

git push origin master
heroku create
git push heroku master

For more options or information, visit heroku documentation or see these blog articles about static content on Heroku with PHP and Apache,  Ruby and Rack.

It took less than half an hour to get static content up and running on Heroku. The service provides nice features, such as .htaccess and scripting in languages like PHP, Ruby, Python and more.

Here is our complete Spring Cleaning list.

Get started today with a 14–day FREE trial.

No obligations, no credit card required.

Get Started Now

About the author

Titas Norkunas

Get updates about development, productivity, and teamwork