Structure of Heroku PaaS allows the advanced user to tweak to some extent within a PaaS environment. Tips For Command Line Interface possibly will help more. For just the starters, the guide Step by Step Guide to Use Free Heroku Cloud is more than enough as text guide to get started to use Heroku Cloud, Advanced Commands for Perfect Setup is somewhat for the advanced users for custom setup. Obviously, you need to know the reality about PaaS or rather the inherited limitations of a PaaS by structure, compared to an IaaS / Cloud Server. This article on Structure of Heroku PaaS allows the advanced user is for someone possibly more academic to explore the more possibilities of Heroku PaaS.
Structure of Heroku PaaS : Some Important Links
In the web, it is impractical to think, not to mention the others’ writings ; in order to make the reader understanding the things. Heroku itself has a quite good webpage where they have explained the structure of Heroku PaaS, at least the basics in a graphical way :
|
1 |
http://www.heroku.com/how/connect |
The reason not to use hyperlinks to other websites is not the ‘fear’ of losing visitors from this webpage, but to nullify we as the referrer to protect the privacy of the user.
---
As everyone knows, SalesForce is the company behind Heroku :
|
1 |
http://www.salesforce.com/heroku/ |
It is just to allay the anxiety of the new users about who runs it. It is improbable that, Heroku will cease to deliver the free usage tier, mostly because, its the free usage tier that basically pushes all the developers to develop new ways.
Structure of Heroku PaaS : Tips For Command Line Interface
We are deliberately avoiding some terminologies in this article. First login to Heroku Cloud normally from command line interface. The emulator software can be Terminal, iTerm2 or that Bash application that comes with Windows version of Heroku Toolbelt. If you run :
|
1 |
heroku run bash |
command, after changing directory (cd followed by folder-name command) to an existing or newly created app on Heroku, you can actually execute some commands more than you usually do on normal login. exit command exits this bash interface. If you run pwd command, it will show that, you are inside the app folder. Run :
|
1 |
cd / |
And run ls command. Now if you cd to that app folder and do ls, it will show up four folders and one file (boot.sh). You can Apache mod_rewrite to serve content out of “webroot” on Heroku. We basically have shown another way to set the web folder in previous guide.
|
1 |
RewriteEngine On |
|
1 |
RewriteRule ^.htaccess$ - [F] |
|
1 |
RewriteCond %{REQUEST_URI} ="" |
|
1 |
RewriteRule ^.*$ /webroot/index.php [NC,L] |
|
1 |
RewriteCond %{REQUEST_URI} !^/webroot/.*$ |
|
1 |
RewriteRule ^(.*)$ /webroot/$1 RewriteCond %{REQUEST_FILENAME} -f |
|
1 |
RewriteRule ^.*$ - [NC,L] |
|
1 |
RewriteRule ^public/.*$ /webroot/index.php [NC,L] |
I copied it from StackOverFlow user fixlr’s one answer.
Now, if you cd to /bin and do an ls, you will get some names. As an UNIX or Linux/ Unix like OS user, you will understand that they are commands. Unfortunately not all command are executable with user level privilege.
/a
