From ffcb2ed4ac334a0c58986c375ebaf4e3e47cf3e5 Mon Sep 17 00:00:00 2001 From: Tim Robinson Date: Thu, 20 Nov 2014 15:10:03 +0000 Subject: [PATCH 01/33] Add doc for setting up PHPMyAdmin --- src/persistence/setting_up_phpmyadmin.md | 24 ++++++++++++++++++++++++ templates/default/toc.jade | 3 +++ 2 files changed, 27 insertions(+) create mode 100644 src/persistence/setting_up_phpmyadmin.md diff --git a/src/persistence/setting_up_phpmyadmin.md b/src/persistence/setting_up_phpmyadmin.md new file mode 100644 index 0000000..7363f8b --- /dev/null +++ b/src/persistence/setting_up_phpmyadmin.md @@ -0,0 +1,24 @@ +# PHPMyAdmin + +PHPMyAdmin provides an easy to use web interface to manage your MySQL database/s + +## PHPMyAdmin's most common features +* Import data from CSV and SQL +* Export data to various formats: CSV, SQL, XML, PDF (via the TCPDFfd\mya library), ISO/IEC 26300 - OpenDocument Text and Spreadsheet, Word, Excel, LaTeX and others +* Administering multiple servers +* Creating PDF graphics of the database layout +* Creating complex queries using Query-by-Example (QBE) +* Searching globally in a database or a subset of it +* Transforming stored data into any format using a set of predefined functions, like displaying BLOB-data as image or download-link +* Live charts to monitor MySQL server activity like connections, processes, CPU/Memory usage, etc. +* [Many more](http://en.wikipedia.org/wiki/PHPMyAdmin)
+ +## Using PHPMyAdmin with Cloud9 +This article explains our first iteration of PHPMyAdmin support in Cloud9. It makes it super easy to install a PHPMyAdmin instance right in your workspace. Each workspace runs it's own Database and copy of PHPMyAdmin. + +```bash +# Install PHPMyAdmin +$ phpmyadmin-ctl install +``` + +After the installation is complete you'll be given a link to access PHPMyAdmin. If you'd like further help using the software please consult the official PHPMyAdmin docs. \ No newline at end of file diff --git a/templates/default/toc.jade b/templates/default/toc.jade index 329334a..17441af 100644 --- a/templates/default/toc.jade +++ b/templates/default/toc.jade @@ -154,6 +154,9 @@ ul li.nav-submenu-item a(href='setting_up_mysql.html') Using MySQL + ul + li.nav-submenu-item + a(href='setting_up_phpmyadmin.html') Using PHPMyAdmin li.nav-submenu-item a(href='setting_up_mongodb.html') Using MongoDB li.nav-submenu-item From fb3c17899560d40fa434ec0f61b60b2810c9f676 Mon Sep 17 00:00:00 2001 From: Tim Robinson Date: Thu, 20 Nov 2014 15:28:03 +0000 Subject: [PATCH 02/33] Minor tweaks to article Conflicts: out/cloud9-user-documentation.json out/index.html out/setting_up_phpmyadmin.html recentFiles.json --- out/cloud9-user-documentation.json | 418 ++++++++++++----------- out/index.html | 14 +- out/setting_up_phpmyadmin.html | 228 +++++++++++++ recentFiles.json | 2 +- src/persistence/setting_up_phpmyadmin.md | 5 +- 5 files changed, 452 insertions(+), 215 deletions(-) create mode 100644 out/setting_up_phpmyadmin.html diff --git a/out/cloud9-user-documentation.json b/out/cloud9-user-documentation.json index 76207ae..9ca06f7 100644 --- a/out/cloud9-user-documentation.json +++ b/out/cloud9-user-documentation.json @@ -2,462 +2,468 @@ "files": [ { "filename": "deploying_code", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Deploying Your Code", "contents": "\n

Deploying Your Code

\n

Cloud9 IDE offers many different ways to get your code from your editor to your \nproduction server. To deploy your code, click on the Deploy button in the \nProject Bar:

\n

\"The

\n

We offer tight integration with the following environments:

\n\n

Following these links will provide you with more information on code deployment.\nYou can deploy your code to as many services and servers as you like. Keep in \nmind that you'll already need an account at those hosting providers before you \ncan deploy your app to them!

\n

If you're comfortable with the command line, you can also deploy to several more\nenvironments, such as:

\n\n

Warning:

Before you attempt to deploy your application, make sure that you have \ncommitted all your changes to version control. Cloud9 deploys for you whatever \nwas last committed to version control.
\n\n
" }, { "filename": "deploying_to_heroku", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Deploying to Heroku", "contents": "\n

Deploying to Heroku

\n

This section will show you how to deploy your applications to Heroku, a cloud-based application platform. The integration with Cloud9 IDE makes your development process even more agile. If you don't have a Heroku account, visit their website to create one for free.

\n

To get started, create a simple Node.js application. If you don't have one yet, you can follow our tutorial on developing one.

\n

After you click on the Deploy button in the Project Bar, click the plus sign next to Deploy to add another deploy target. Choose Heroku as an option. After you have signed into your Heroku account, you can create a new deploy target or choose an existing one from your account:

\n

\"Showing

\n

Note:

Heroku only allows you to create names for your apps that contain letters and dashes.\n\n
\n

Next, press Deploy to continue the process; the following window might appear:

\n

\"Dialog

\n

Heroku Node.js apps are required to have a package.json file, much like with NPM. Cloud9 can generate a package.json file for you, containing metadata to share Heroku. The following lines represent what that file might looks like:

\n
{\n    \"name\": \"cloud9-heroku-example\",\n    \"version\": \"0.0.1\"\n}
\n

After you have a package.json file, you might see this dialog:

\n

\"Dialog

\n

Sometimes, a Heroku app also requires a Procfile. The Procfile is needed to start the application in Heroku. You can just create a new file, add the line below, and save it as 'Procfile'. Don't add any file extensions.

\n
web: node web.js
\n

Try the deploy button again. The console will directly output the following when the deployment is completed:

\n

\"Console

\n

And just like that, you've deployed your project to Heroku.

\n\n
" }, { "filename": "deploying_to_windows_azure_sites", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Deploying to Windows Azure Sites", "contents": "\n

Deploying to Windows Azure Sites

\n

This article will show you how to deploy your applications to Windows Azure. If you don't have an account yet, the Windows Azure process will help you create one. Keep in mind that Windows Azure is not free, though it does come with a free trial. Windows Azure projects can be deployed from any operating system.

\n

To get started, create a simple Node.js application. If you don't have one yet, you can follow our tutorial on developing one.

\n

After you click on the Deploy button in the Project Bar, click the plus sign next to Deploy to add another deploy target. Choose Windows Azure as an option. You'll be prompted with this dialog:
\"Windows

\n

You must click on the Download Windows Azure Settings button before you can continue. If you don't have a Windows Azure account, here is where you can create one. If you do have an account, your browser will automatically download the required file.

\n

When that's finished, simply select the downloaded file from your computer, and upload it to Cloud9. You'll only have to do this process once. If you ever need to upload a new certificate, be sure to click Clear cert in the lower-right corner of this dialog.

\n

After the file has uploaded, click on Create new to create a new hosted service. A hosted service is the container in which your application is hosted when it is deployed to Windows Azure. For more information, see Overview of Creating a Hosted Service for Windows Azure.

\n

You can set a few configuration options such as the number of instances to use, its host OS, and where the data center is located. Selecting "Enable RDP" and providing a username and password enables remote desktop for your deployment.

\n

Your new Windows Azure server will appear in the Deploy list:
\"Windows

\n

Go ahead and click on DEPLOY. If this is the first time you're trying to deploy this project to Windows Azure, you'll receive three prompts:

\n
    \n

  1. A dialog will inform you of a missing web.config file. If you click Yes, Cloud9 will create a file called Web.cloud.config in your project. This file contains configuration information about your app.

    \n
    2. \n

  2. You'll be told about a missing csdef file. If you click Yes, Cloud9 will create a file called ServiceDefinition.csdef in your project. ServiceDefinition.csdef is a Windows Azure-specific files necessary for publishing your application For more information, see Overview of Creating a Hosted Service for Windows Azure.

    \n
    3. \n

  3. You'll be asked to select the instance size for this application. For this tutorial, just select Small, and then click Create. For more details about Windows Azure VM sizes, see How to Configure Virtual Machine Sizes.

    \n
    4. \n
\n

Your app will now deploy to a Windows Azure server! You can follow its progress in the Deploy panel, or by watching the messages in the console:\n\"Windows

\n

For more information on configuring your app on the Windows Azure website, see Deploying a Windows Azure App from Cloud9.

\n\n
" }, { "filename": "deploying_via_cli", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Deploying via the Command Line", "contents": "

Deploying via the Command Line

\n

In the new version of Cloud9 we don't have support for deployment from the UI yet, but we're going to add those features soon.

\n

Until then, you can manually install various command-line tools into your workspace and deploy using the command line. \nIt should go without saying that this is for super 31337 developers that aren't afraid of the command line.

\n

Below is a list of some of the services we have tested and support deploying to. \nAll the commands need to be executed in the terminal unless stated otherwise.

\n

Heroku

\n

Heroku's toolbelt is installed by default in new VMs.

\n

Now, you can use the heroku command for your projects, as described in the \nHeroku documentation.

\n

If deploying to Heroku, you should probably be using a local instance of PostgresQL, or you may run into problems caused by different database interpretations of SQL.

\n

Windows Azure Web Sites

\n

Free and Premium Plans

\n

In the Console or a Terminal, type the \nfollowing:

\n
npm install azure
\n

Now, you can use the azure command from the Console/Terminal. For more \ninformation, read the official azure documentation.

\n

Premium Plans

\n

To deploy to Azure sites from the command line, open the Terminal and type:

\n
cd ~/lib/azure-sites\nnpm install
\n

Then, add the bin to your workspace's path:

\n
PATH=$PATH:$HOME/lib/azure-sites/bin
\n

Now, you can use the azure command in the terminal.

\n

Windows Azure Cloud Services

\n

For free and premium plans, follow the instructions on the \nazure-cmdlet-node repository. This \nproject is maintained by Cloud9.

\n

Google App Engine

\n

First, setup Push to Deploy: Create a new App Engine application at \ncloud.google.com/console, and then enable \nPush-to-Deploy under 'App Engine' in the Application Settings page. Leave this \ntab open to note the URL for your repo.

\n

Secondly, configure Cloud9. Run the following commands (making sure to replace \nyour email address, auth-token, and repo-url):

\n
echo \"machine code.google.com login EMAIL password PASSWORD\" >> ~/.netrc\ngit remote add appengine REPO
\n

Note:

The email in this case is the mail address you use to login to your Google\nApp Engine account and the password is the auth-token generated from the admin\nconsole, it is not your google password, never type that into a third party tool.\n'REPO' is the repository URL generated before.\n\n
\n

Finally, do a commit, and a push:

\n
git commit -a -m \"First commit\"\ngit push appengine master
\n

OpenShift

\n
# Install rhc:\ngem install rhc\nrhc setup\n\n# After this you can use rhc to manage your account:\n\n# list apps:\nrhc apps\n# To show what you can do with apps do:\nrhc app help\n# You deploy via a git push\ngit push <giturl> master
\n

CloudFoundry

\n

To deploy to CloudFoundry from the command line in the Console \nor a Terminal, type:

\n
cd ~\nwget https://github.com/cloudfoundry/vmc/zipball/master\nmv master cloudfoundry\nunzip cloudfoundry\ncd cloudfoundry-vmc-nnnn\nbundle
\n

NodeJitsu

\n

Free and Premium Plans

\n

In the the Console or a Terminal, type:

\n
npm install jitsu@0.7.x -g\nmkdir node_modules\nmv ../lib/node_modules/jitsu node_modules
\n

Now, you can run jitsu from the command line. For more information, see \nthe official jitsu documentation.

\n

Premium Plans

\n
npm install jitsu@0.7.x -g
\n

You can now run jitsu from both the Console and the Terminal.

\n

Modulus

\n

In the the Console or a Terminal, type:

\n
npm install modulus -g
\n

Now, you can run modulus from the command line. For more information, see \nthe official modulus documentation.

\n\n
" }, { "filename": "faq_general", - "mtime": 1416998245000, + "mtime": 1416491265000, "pageTitle": "FAQ: General", - "contents": "

FAQ: General

\n

Can I use FTP workspaces on Cloud9?

\n

Yes, Cloud9 supports FTP workspaces that allow you to edit your files directly on your FTP server. \nCurrently FTP workspaces still open in the old version of Cloud9, but soon we'll also support FTP workspaces with the new version of Cloud9.

\n

One thing that was removed for reliability reasons in the new version of Cloud9, is the ability to deploy over FTP from a regular workspace.\nWe're bringing back those features in a new format and with much higher reliability in the coming months.

\n

How do I deploy to Heroku/Openshift/Azure/...?

\n

See Deploying via CLI.

\n

Can I connect to SMTP servers (port 25)?

\n

No, this is not supported by our hosting platform. It does currently allow access to the GMail servers though, so you can use that service during development.

\n

My workspace says it's out of quota. how do I fix it?

\n

You can inspect your current quota usage with the df command in the Terminal:

\n
$ df
\n

To find which files and directories are consuming a lot of space, go to a directory such as your home directory, and run this command:

\n
$ du -m -d 1 -a | sort -n
\n

This should give you a list of all members of that directory and how much space they use in megabytes.

\n

Alternatively, try du-c9 for seeing all files you added to your workspace and account for the quota.

\n

Can I use two-factor authentication with Cloud9?

\n

You can sign into Cloud9 with your github or bitbucket account and set that up to use two-factor authentication.\nWe don't currently provide an option to directly setup your Cloud9 account for two-factor authentication.

\n

I can't preview my running app.

\n

Try using port 8080 instead, which often solves this case.

\n

EADDRINUSE: My app complains that the address/port is in use

\n

Applications won't start if another application is already listening to the same port. In order to fix it you first need to find out which process that is:

\n
$ netstat -nlp | grep $PORT
\n

This will report the process id (PID) which you can then kill using

\n
$ sudo kill -9 <PID>
\n

Often apache is still running in the background. In that case you can kill it using

\n
$ sudo pkill apache2
\n

How can I upload local files to my project?

\n

Either drag a local file directly from your desktop into the Cloud9 file tree,\nor use the "File > Upload Local Files" menu item.

\n

How can I download my project files?

\n

Use "File > Download project". Currently, this will give you a .tar.gz file, which\nensures maximum portability. To open these files, you can use something like\nWinRAR or 7-zip.

\n

How can I share a single directory of a private workspace

\n

Sometime you might want others to open a file or directory in the browser \nwithout opening up the whole workspace. This can be done by starting a small \nhttp server in that directory and make sure that the running application is public.

\n

To make the running application public you have to click the "sharing" button at\nthe top right and the check "public" for application.

\n

To run the server open a terminal and do

\n
$ cd /dir/i/want/to/share\n$ python3 -m http.server 8080
\n\n
" - }, - { - "filename": "faq_ssh", - "mtime": 1416998221000, - "pageTitle": "FAQ: SSH workspaces", - "contents": "

FAQ: SSH workspaces

\n

I cannot create a SSH workspace using a Digital Ocean droplet

\n

We recently discovered our web host is blocking connections to some Digital Ocean IP addresses because they suspect they are being used by Iranian users. They are legally forced to block them.

\n

Digital Ocean maintains a whitelist of droplet IP addresses which should not be blocked and our web host follows this list.

\n

Please raise a support ticket with Digital Ocean mentioning that you would like to have your droplet IP added to the whitelist. After this is complete you will be able to create your SSH workspace within 24 - 48 hours.

\n

I'm getting an error on the SSH install script: "ncurses not found"

\n

Try executing the following command:

\n
yum install ncurses-devel
\n

or

\n
yum install glibc-static
\n\n
" + "contents": "

FAQ: General

\n

Can I use FTP workspaces on Cloud9?

\n

Yes, Cloud9 supports FTP workspaces that allow you to edit your files directly on your FTP server. \nCurrently FTP workspaces still open in the old version of Cloud9, but soon we'll also support FTP workspaces with the new version of Cloud9.

\n

One thing that was removed for reliability reasons in the new version of Cloud9, is the ability to deploy over FTP from a regular workspace.\nWe're bringing back those features in a new format and with much higher reliability in the coming months.

\n

How do I deploy to Heroku/Openshift/Azure/...?

\n

See Deploying via CLI.

\n

Can I connect to SMTP servers (port 25)?

\n

No, this is not supported by our hosting platform. It does currently allow access to the GMail servers though, so you can use that service during development.

\n

My workspace says it's out of quota. how do I fix it?

\n

You can inspect your current quota usage with the df command in the Terminal:

\n
df
\n

To find which files and directories are consuming a lot of space, go to a directory such as your home directory, and run this command:

\n
du -m -d 1 -a | sort -n
\n

This should give you a list of all members of that directory and how much space they use in megabytes.

\n

Alternatively, try du-c9 for seeing all files you added to your workspace and account for the quota.

\n

I can't preview my running app.

\n

Try using port 8080 instead, which often solves this case.

\n

How can I upload local files to my project?

\n

Either drag a local file directly from your desktop into the Cloud9 file tree,\nor use the "File > Upload Local Files" menu item.

\n

How can I download my project files?

\n

Use "File > Download project". Currently, this will give you a .tar.gz file, which\nensures maximum portability. To open these files, you can use something like\nWinRAR or 7-zip.

\n\n
" }, { "filename": "faq_php", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "FAQ: PHP", "contents": "

FAQ: PHP

\n

where are the Apache logs?

\n

By default the logs are in ~/lib/apache2/log

\n

Is mail() supported?

\n

No, this is currently not supported; see FAQ: General about SMTP access.

\n\n
" }, { "filename": "faq_python", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "FAQ: Python", "contents": "

FAQ: Python

\n

Why does easy_install report a permission_denied error?

\n

Please use sudo easy_install instead.

\n\n
" }, { - "filename": "colorpicker", - "mtime": 1412172002000, - "pageTitle": "Color Picker", - "contents": "\n

Color Picker

\n

Note:

this feature is deprecated\n\n
\n
\n\n
\n\n

The color picker is an awesome feature in Cloud9 IDE, designed to not only make color selections easier, but also, more harmonious. At its core, the color picker is a way to represent words (red, blue, e.t.c.), RGBA values (rgba(175, 3, 124, .6)), or hex values (#f00f00) into actual colors.

\n

To enable the color picker, flip the preferences on in the Settings panel. You can use the color picker in CSS, SVG, HTML, or APF Skin files. All you have to do is hover over the value of a color definition, and it'll instantly highlight, like this: \"Color

\n

When the represented color is highlighted, click on it. You'll get a color square defining all the possible color arrangements. To select a color, you can click in the square, pick your own RGB or HSB values, or enter some hex code. Best of all, at the bottom of the window, you'll find a list of other colors found within the same document--just in case you want to achieve matching shades:
\"Color

\n

To set the value, just click anywhere outside of the color picker.

\n\n
" - }, - { - "filename": "language_analysis", - "mtime": 1412172002000, - "pageTitle": "Language Analysis", - "contents": "

Language Analysis

\n

For JavaScript files, Cloud9 provides analysis using a combination of our own analysis tools, as well as JSHint (specifically for Javascript code). Our language analysis can't detect if your program is correct, fast, or has memory leaks, but it can save you time by spotting things like undeclared variables, syntax errors, or other preventable typos.

\n

When Cloud9 detects an issue with your code, an icon appears in the gutter for the offending lines of code. There are three types of identifiers available for your code:

\n
    \n
  • Informational (\"Little): these are non-critical, non-dangerous updates about your code
    • \n
  • Warnings (\"Warning): these are potentially incorrect pieces of code
    • \n
  • Errors (\"Error): these are incorrect lines of code that will almost certainly throw a runtime error when you try to run your script
    • \n
\n

If you hover over any of these icons in the gutter, you'll get a pop-up that presents some information as to what, exactly, the problem is. For example, suppose we have a variable declared, called fs, that is never used:
\"fs

\n

Notice also that fs has a strikethrough, to provide further visual clues that something is not quite right.

\n

If you're concerned with the level of information that's listed in the gutter, you can always configure its "strictness" in the IDE preferences. For example, you could choose to hide every icon that isn't a warning or an error.

\n

Configuring Global Options

\n

JSHint provides additional configuration options that Cloud9 incorporates on a per-file basis. Typically, you declare these options as comments at the very top of a file, like this:

\n
/*jshint curly:true, debug:true */
\n

For a full list of the JSHint configutation options, please check the documentation page describing them.

\n\n
" + "filename": "faq_ssh", + "mtime": 1416491265000, + "pageTitle": "FAQ: SSH workspaces", + "contents": "

FAQ: SSH workspaces

\n

I cannot create a SSH workspace using a Digital Ocean droplet

\n

We recently discovered our web host is blocking connections to some Digital Ocean IP addresses because they suspect they are being used by Iranian users. They are legally forced to block them.

\n

Digital Ocean maintains a whitelist of droplet IP addresses which should not be blocked and our web host follows this list.

\n

Please raise a support ticket with Digital Ocean mentioning that you would like to have your droplet IP added to the whitelist. After this is complete you will be able to create your SSH workspace within 24 - 48 hours.

\n

I'm getting an error on the SSH install script: "ncurses not found"

\n

Try executing the following command:

\n
yum install ncurses-devel
\n

or

\n
yum install glibc-static
\n\n
" }, { "filename": "autocompletion", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Code Autocompletion", "contents": "\n

Code Autocompletion

\n

For Javascript programs, Cloud9 IDE provides intelligent and responsive autocompletion for your code. Autocompletion is based not only on the content within your files, but also on the ECMAScript and Node.js standard library:

\n

\"Autocompletion

\n

Methods defined in ECMAScript and Node.js also have documentation provided for you. Simply hover over a method name for a moment, and a second box quickly shows some additional information.

\n

You can disable autocompletion in the Settings menu.

\n\n
" }, + { + "filename": "collaboration", + "mtime": 1416491265000, + "pageTitle": "Collaboration", + "contents": "

Collaboration

\n

Note:

this article is outdated, a new version will follow soon\n\n
\n

Collaboration with Cloud9 IDE is an amazing feature that lets you do more than just share your projects with any other Cloud9 developer. You can grant someone else access to change files in your workspace, in realtime--or just let them view the workspace without any other rights. While you're collaborating, you can discuss the code through a built-in chat room.

\n

To invite someone to collaborate on a project with you, simply copy the URL in the browser and send it to a friend. You can also click on Share in the menu bar to get quick access to other ways to share, such as via e-mail, Twitter, or Facebook.

\n

Let's take a look at some of the additional features available while you collaborate.

\n

Members List

\n

There are two terms used for people accessing your project: members and visitors. Members are individuals that have read and write access to your project--that means they can change any code; visitors only have read access. The Members panel lists all the collaborators in a project, both active and inactive:

\n

\"The

\n

If you are the owner of a project, you can click on anyone's username to grant (or revoke) write access:

\n

\"Granting

\n

If you're worried about the sanctity of your code after grant access to other developers, fear not. You can always take a look at a file revision history to view line-by-line changes made to your project over time.

\n

Chatting

\n

Any member or visitor can participate in group chat with each other. Developers can also choose to double-click on a person's username and engage in a private, instant-message-style conversation.

\n

Collaborate on Code

\n

When a collaborator changes a file you're also working on, Cloud9 detects it and asks you whether you'd like to use their changes, or your version. We're also simply giving you the option to merge both, using a three-way-merge algorithm to handle any conflicts. This is the same algorithm used by version control systems like git for merging branches.

\n

To make the experience even smoother you can choose "Always merge by default" and we'll never interrupt you about file changes again.

\n

Check out the video below to see this in action.

\n
\n\n
\n\n
" + }, + { + "filename": "colorpicker", + "mtime": 1416491265000, + "pageTitle": "Color Picker", + "contents": "\n

Color Picker

\n

Note:

this feature is deprecated\n\n
\n
\n\n
\n\n

The color picker is an awesome feature in Cloud9 IDE, designed to not only make color selections easier, but also, more harmonious. At its core, the color picker is a way to represent words (red, blue, e.t.c.), RGBA values (rgba(175, 3, 124, .6)), or hex values (#f00f00) into actual colors.

\n

To enable the color picker, flip the preferences on in the Settings panel. You can use the color picker in CSS, SVG, HTML, or APF Skin files. All you have to do is hover over the value of a color definition, and it'll instantly highlight, like this: \"Color

\n

When the represented color is highlighted, click on it. You'll get a color square defining all the possible color arrangements. To select a color, you can click in the square, pick your own RGB or HSB values, or enter some hex code. Best of all, at the bottom of the window, you'll find a list of other colors found within the same document--just in case you want to achieve matching shades:
\"Color

\n

To set the value, just click anywhere outside of the color picker.

\n\n
" + }, + { + "filename": "git_blame", + "mtime": 1416491265000, + "pageTitle": "Git Blame", + "contents": "\n

Git Blame

\n

Note:

this feature is deprecated\n\n
\n
\n\n
\n\n

When you're working with git repositories, it's helpful to know who made a commit to a particular piece of code. As it turns out, git has a feature called git blame that we've integrated directly into Cloud9 IDE.

\n

By using git blame, you'll be able to instantly discover who edited certain lines of code, when they edited it, and what their commit message at the time was. Clicking on a git commit also highlights other lines of code changed at the same time. To launch the git blame feature, open a file and navigate to Tools > Git > Blame.

\n\n
" + }, { "filename": "custom_runners", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Custom Runners", "contents": "

Custom Runners

\n

Luckily you're not limited to the default set of Runners in Cloud9.\nYou can simply define your own custom Runner, which is both simple and very powerful.\nAll you need to do is create a Runner file.\nIn this article we'll describe how to do this in just a few steps.

\n

In the Run panel (usually at the bottom of the UI), click the 'Runner' text input and choose 'New Runner'. \nIn the new Runner file that's now opened, you can configure your runner\nusing a simple JSON format. We'll show a basic example below\nand then explain the different properties you can use.

\n

Let's start with a basic example: a runner for go files.

\n
{\n    \"cmd\": [\"go\", \"run\", \"$file\", \"$args\"],\n    \"selector\": \"source.go\",\n    \"info\": \"Your code is running :)\"\n}
\n

This runner will use "go run" for any file that has a ".go" file extension.\nIf you add it, it'll override our default Go runner.

\n

As another example, let's save a new Node 0.11 configuration, including Harmony support. \nCreate a new Runner, add this code, and save it as 'Node 0.11.x.run':

\n
// This file overrides the built-in Node 0.11.x runner\n// For more information see http://docs.c9.io:8080/#!/api/run-method-run\n{\n  \"cmd\": [\n    \"bash\",\n    \"--login\",\n    \"-c\",\n    \"nvm use 0.11 > /dev/null; node --harmony ${debug?--nocrankshaft --nolazy --debug-brk=15454} '$file' $args\"\n  ],\n  \"debugger\": \"v8\",\n  \"debugport\": 15454,\n  \"info\": \"Your code is running at \\\\033[01;34m$url\\\\033[00m.\\n\\\\033[01;31mImportant:\\\\033[00m use \\\\033[01;32mprocess.env.PORT\\\\033[00m as the port and \\\\033[01;32mprocess.env.IP\\\\033[00m as the host in your scripts!\\n\"\n}
\n

Note:

alternatively, you can check 'Show Hidden Files' in your workspace directory tree (the small gear in the upper right corner), and create a new file in the '.c9/runners' folder called 'Node 0.11.x.run' with this code.\n\n
\n

That's it! Your custom Runner should be available in the Run panel.

\n

Runner Variables

\n

Here's a list of all the variables you can use in your runners:

\n
    \n

  • $file_path The directory of the current file, e. g., /home/ubuntu/workspace/docs

    \n
    • \n

  • $file The full path to the current file, e. g., /home/ubuntu/workspace/docs/Chapter1.txt.

    \n
    • \n

  • $args Any arguments entered after the file name.

    \n
    • \n

  • $file_name The name portion of the current file, e. g., Chapter1.txt.

    \n
    • \n

  • $file_extension The extension portion of the current file, e. g., txt.

    \n
    • \n

  • $file_base_name The name only portion of the current file, e. g., Document.

    \n
    • \n

  • $packages The full path to the Packages folder.

    \n
    • \n

  • $project The full path to the current project file.

    \n
    • \n

  • $project_path The directory of the current project file.

    \n
    • \n

  • $project_name The name portion of the current project file.

    \n
    • \n

  • $project_extension The extension portion of the current project file.

    \n
    • \n

  • $project_base_name The name only portion of the current project file.

    \n
    • \n

  • $hostname The hostname of the workspace.

    \n
    • \n

  • $hostname_path The hostname of the workspace together with the relative path of the project file.

    \n
    • \n

  • $url The full url to access the workspace.

    \n
    • \n

  • $port The port assigned to the workspace.

    \n
    • \n

  • $ip The ip address to run a process against in the workspace.

    \n
    • \n
\n\n
" }, { "filename": "gotofile_and_definition", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Using Goto File and Goto Definition", "contents": "\n

Using Goto File and Goto Definition

\n

Note:

this article is outdated, a new version will follow soon\n\n
\n
\n\n
\n\n

Let's say you're working a large project containing many files, and you kind-of sort-of know the name of a file that you want to open up. Goto File is our feature to help you quickly and easily jump to any file in your workspace, without the need to search through different directories. Simply hit Cmd-E (or Ctrl-E on Unix/Windows) and away you go:

\n

\"Goto

\n

Goto File offers filtering for any portion of a filename, including directories. Search for the beginning, middle, or end of a file path, or even just an extension, like .js, and Goto File with instantly present the results to you. Clicking on a name in the list opens the file right up. Goto File does not support case-insensitive, wildcard (*, ?), or regular expression (., +) searching.

\n

Goto Definition takes the same concept and applies it to files. You can easily navigate between classes and members defined in your files. By entering text, you can filter your class' member results. Finally, as you navigate through your file, Cloud9 IDE will jump to the relevant portion of the code:

\n

\"Goto

\n

Note:

Currently, Goto Definition only works for Javascript files.\n\n
\n

Another feature that's available is the capability to "jump to definition." If your cursor is on a variable or function name, you can tap F12 (or type jumptodef in the console) to instantly scroll the editor to the member's definition.

\n\n
" }, { - "filename": "collaboration", - "mtime": 1412172002000, - "pageTitle": "Collaboration", - "contents": "

Collaboration

\n

Note:

this article is outdated, a new version will follow soon\n\n
\n

Collaboration with Cloud9 IDE is an amazing feature that lets you do more than just share your projects with any other Cloud9 developer. You can grant someone else access to change files in your workspace, in realtime--or just let them view the workspace without any other rights. While you're collaborating, you can discuss the code through a built-in chat room.

\n

To invite someone to collaborate on a project with you, simply copy the URL in the browser and send it to a friend. You can also click on Share in the menu bar to get quick access to other ways to share, such as via e-mail, Twitter, or Facebook.

\n

Let's take a look at some of the additional features available while you collaborate.

\n

Members List

\n

There are two terms used for people accessing your project: members and visitors. Members are individuals that have read and write access to your project--that means they can change any code; visitors only have read access. The Members panel lists all the collaborators in a project, both active and inactive:

\n

\"The

\n

If you are the owner of a project, you can click on anyone's username to grant (or revoke) write access:

\n

\"Granting

\n

If you're worried about the sanctity of your code after grant access to other developers, fear not. You can always take a look at a file revision history to view line-by-line changes made to your project over time.

\n

Chatting

\n

Any member or visitor can participate in group chat with each other. Developers can also choose to double-click on a person's username and engage in a private, instant-message-style conversation.

\n

Collaborate on Code

\n

When a collaborator changes a file you're also working on, Cloud9 detects it and asks you whether you'd like to use their changes, or your version. We're also simply giving you the option to merge both, using a three-way-merge algorithm to handle any conflicts. This is the same algorithm used by version control systems like git for merging branches.

\n

To make the experience even smoother you can choose "Always merge by default" and we'll never interrupt you about file changes again.

\n

Check out the video below to see this in action.

\n
\n\n
\n\n
" - }, - { - "filename": "searching_in_files", - "mtime": 1412172002000, - "pageTitle": "Searching and Replacing in Files", - "contents": "

Searching and Replacing in Files

\n
\n\n
\n\n

Aside from Goto File and Goto Definition, Cloud9 also offers more traditional search functionality. There are three types of search modes available: quicksearch, search and replace, and find in files.

\n

Quicksearch

\n

Quicksearch can be activated by hitting Cmd-F on a Mac, or Ctrl-F on a Unix/Windows machine. As you type in the quicksearch bar, the IDE instantly shifts to the next available result. This is a great way to quickly search around in your code without hassle.

\n

Quicksearch offers the following options:

\n
    \n
  • Regular Expressions: when enabled, your search is treated as a regular expression
    • \n
  • Match Case: when enabled, your search takes capitalizations seriously:
    • \n
  • Whole Words: when enabled, your search will only be considered for whole words:
    • \n
  • Search Backwards: when enabled, the search goes backwards, instead of forwards
    • \n
  • Wrap Around: when enabled, the search loops around the file, from bottom to top
    • \n
  • Search Selection: when enabled, the search only considers code that you've currently highlighted
    • \n
\n

Search and Replace

\n

Building on the features of quicksearch, search and replace allows you to replace segments of code in your file. You can again continue to use regular expressions, keeping in mind the groupings are prefixed with a dollar sign, i.e. $1.

\n

Replacing offers two more options:

\n
    \n
  • Preserve Case: if enabled, case is preserved while replacing content
    • \n
  • Highlight Matches: if enabled, the new replaced matches are highlighted in the document
    • \n
\n

Find in Files

\n

In order to search across a set of files, you'll want to use the Find in Files feature. Here, you can search of a string or regular expression, within your entire workspace or a single directory. You can also filter based on extensions, like *.js or *.rb.

\n

Find in files offers some of the same search options as quicksearch:

\n
    \n
  • Regular Expressions: when enabled, your search is treated as a regular expression
    • \n
  • Match Case: when enabled, your search takes capitalizations seriously
    • \n
  • Whole Words: when enabled, your search will only be considered for whole words
    • \n
\n

One more feature of find in files is the ability to render search results either in the console or the IDE. You can fold results to keep them out of the way, or, edited the file if you're working down a list:
\"Search

\n\n
" + "filename": "language_analysis", + "mtime": 1416491265000, + "pageTitle": "Language Analysis", + "contents": "

Language Analysis

\n

For JavaScript files, Cloud9 provides analysis using a combination of our own analysis tools, as well as JSHint (specifically for Javascript code). Our language analysis can't detect if your program is correct, fast, or has memory leaks, but it can save you time by spotting things like undeclared variables, syntax errors, or other preventable typos.

\n

When Cloud9 detects an issue with your code, an icon appears in the gutter for the offending lines of code. There are three types of identifiers available for your code:

\n
    \n
  • Informational (\"Little): these are non-critical, non-dangerous updates about your code
    • \n
  • Warnings (\"Warning): these are potentially incorrect pieces of code
    • \n
  • Errors (\"Error): these are incorrect lines of code that will almost certainly throw a runtime error when you try to run your script
    • \n
\n

If you hover over any of these icons in the gutter, you'll get a pop-up that presents some information as to what, exactly, the problem is. For example, suppose we have a variable declared, called fs, that is never used:
\"fs

\n

Notice also that fs has a strikethrough, to provide further visual clues that something is not quite right.

\n

If you're concerned with the level of information that's listed in the gutter, you can always configure its "strictness" in the IDE preferences. For example, you could choose to hide every icon that isn't a warning or an error.

\n

Configuring Global Options

\n

JSHint provides additional configuration options that Cloud9 incorporates on a per-file basis. Typically, you declare these options as comments at the very top of a file, like this:

\n
/*jshint curly:true, debug:true */
\n

For a full list of the JSHint configutation options, please check the documentation page describing them.

\n\n
" }, { "filename": "multiple_cursors", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Multiple Cursors", "contents": "\n

Multiple Cursors

\n

Multiple cursors is one of the most useful features available in the Cloud9 editor. You can use multiple cursors to perform tasks like rename several variables or members at once, break up lists separated by commas, or insert the same text in multiple locations.

\n

\"Showing

\n

Multiple selections can be copied and pasted, and you can insert or remove entire lines in several locations.

\n

There are several ways to get access to mutliple cursors:

\n
    \n
  • Via keyboard shortcuts, you can create a new cursor in any direction
    • \n
  • By holding the Alt key, clicking the mouse, and dragging the cursor up or down in the editor
    • \n
  • Through the menu bar at Selection > Multiple Selections
    • \n
\n

One of the best capabilities is the ability to instantly select the next instance of your currently highlighted section. This is especially useful for refactoring several parts of the code at once. To do this, press Ctrl-Alt, followed by the right (or left) arrow key to navigate around in the code.

\n\n
" }, + { + "filename": "revisions", + "mtime": 1416491265000, + "pageTitle": "Revisions", + "contents": "\n

Revisions

\n

Note:

this article is outdated, a new version will follow soon\n\n
\n
\n\n
\n\n

Every time you save a file on Cloud9, a diff of any changes made to it is saved by the server. Over time, you can view these file revisions as content is added and removed from your files. You can also restore a file to any previously saved state; you'll never have to worry about losing your work ever again!

\n

To access file revisions, you can either go to File > File Revisions History, or type Cmd-B on Mac or Ctrl-B on Linux/Windows. This will pop open the Revisions History panel. Red lines indicate lines that were removed; green lines indicate lines that were either added or changed.

\n

At the bottom of the panel, there's a checkbox for showing all of a file's changes. Files changes that occur relatively soon to one another--say, a few seconds--are grouped by the revisions panel as one "change." If you prefer to see every single change as an individual entry, enable the Show all file changes checkbox.

\n

To restore a file to a previous revision, simply click the revisions button for that entry: \"Revisions

\n\n
" + }, + { + "filename": "searching_in_files", + "mtime": 1416491265000, + "pageTitle": "Searching and Replacing in Files", + "contents": "

Searching and Replacing in Files

\n
\n\n
\n\n

Aside from Goto File and Goto Definition, Cloud9 also offers more traditional search functionality. There are three types of search modes available: quicksearch, search and replace, and find in files.

\n

Quicksearch

\n

Quicksearch can be activated by hitting Cmd-F on a Mac, or Ctrl-F on a Unix/Windows machine. As you type in the quicksearch bar, the IDE instantly shifts to the next available result. This is a great way to quickly search around in your code without hassle.

\n

Quicksearch offers the following options:

\n
    \n
  • Regular Expressions: when enabled, your search is treated as a regular expression
    • \n
  • Match Case: when enabled, your search takes capitalizations seriously:
    • \n
  • Whole Words: when enabled, your search will only be considered for whole words:
    • \n
  • Search Backwards: when enabled, the search goes backwards, instead of forwards
    • \n
  • Wrap Around: when enabled, the search loops around the file, from bottom to top
    • \n
  • Search Selection: when enabled, the search only considers code that you've currently highlighted
    • \n
\n

Search and Replace

\n

Building on the features of quicksearch, search and replace allows you to replace segments of code in your file. You can again continue to use regular expressions, keeping in mind the groupings are prefixed with a dollar sign, i.e. $1.

\n

Replacing offers two more options:

\n
    \n
  • Preserve Case: if enabled, case is preserved while replacing content
    • \n
  • Highlight Matches: if enabled, the new replaced matches are highlighted in the document
    • \n
\n

Find in Files

\n

In order to search across a set of files, you'll want to use the Find in Files feature. Here, you can search of a string or regular expression, within your entire workspace or a single directory. You can also filter based on extensions, like *.js or *.rb.

\n

Find in files offers some of the same search options as quicksearch:

\n
    \n
  • Regular Expressions: when enabled, your search is treated as a regular expression
    • \n
  • Match Case: when enabled, your search takes capitalizations seriously
    • \n
  • Whole Words: when enabled, your search will only be considered for whole words
    • \n
\n

One more feature of find in files is the ability to render search results either in the console or the IDE. You can fold results to keep them out of the way, or, edited the file if you're working down a list:
\"Search

\n\n
" + }, { "filename": "supported_languages", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Supported Languages", "contents": "

Supported Languages

\n

Cloud9 IDE has varying levels of support for different programming languages. \nUsually you will at least have Syntax Highlighting in the editor and the ability\nto run apps from the Terminal.

\n

Syntax Highlighting

\n

Cloud9 IDE develops and builds on Ace, an \neditor for writing code online. Cloud9's Ace editor currently supports \nhighlighting for about 100 programming languages, and any changes made to Ace are \nreflected back into Cloud9 IDE.

\n

The list of supported languages is growing, and you can get the full list from \nthe View > Syntax menu. Feel free to create an issue in the Ace repository \nfor new requests, or add your own syntax highlighting mode.

\n

See Syntax Highlighting & Themes for more \ninfo.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Running apps

\n

The Run panel currently supports running the following by default:

\n
    \n
  • Apache httpd (PHP, HTML)
    • \n
  • Node
    • \n
  • Python
    • \n
  • Ruby
    • \n
  • Ruby on Rails
    • \n
  • Go
    • \n
  • CoffeeScript
    • \n
  • Julia
    • \n
  • Mocha
    • \n
  • Shell script
    • \n
\n

If you'd like to run any other language, simply create a new "Runner".

\n

You can also do so from the Terminal. \nEach workspace is an Ubuntu VM with the standard tools like bash, make, \ngcc, vim, java SDK or perl pre-installed.

\n\n
" }, { "filename": "syntax_highlighting_themes", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Syntax Higlighting and Themes", "contents": "\n

Syntax Higlighting and Themes

\n
\n\n

Cloud9 IDE develops and builds on Ace, an editor for writing code online. Ace supports over two dozen different themes for highlighting your code, and any changes made to Ace are reflected back into Cloud9 IDE.

\n

You can change your current theme by going to View > Themes, and selecting from one of the many options. By hovering over the menu items, you'll be able to get a preview of the theme. To activate a theme you like, just click on its name.

\n

The IDE contains the following themes:

\n
    \n
  • Chrome
    • \n
  • Clouds
    • \n
  • Clouds Midnight
    • \n
  • Cobalt
    • \n
  • Crimson Editor
    • \n
  • Dawn
    • \n
  • Eclipse
    • \n
  • Idle Fingers
    • \n
  • Kr Theme
    • \n
  • Merbivore
    • \n
  • Merbivore Soft
    • \n
  • Mono Industrial
    • \n
  • Monokai
    • \n
  • Pastel On Dark
    • \n
  • Solarized Dark
    • \n
  • Solarized Light
    • \n
  • TextMate
    • \n
  • Tomorrow
    • \n
  • Tomorrow Night
    • \n
  • Tomorrow Night Blue
    • \n
  • Tomorrow Night Bright
    • \n
  • Tomorrow Night Eighties
    • \n
  • Twilight
    • \n
  • Vibrant Ink
    • \n
\n

By default, files are highlighted based on their file extension. You can change this by going to View > Syntax, and selecting a different context. This forces a single file to use a different highlighter.

\n

We support highlighting for at least the following languages, and many more:

\n
    \n
  • CoffeeScript
    • \n
  • ColdFusion
    • \n
  • C#
    • \n
  • CSS
    • \n
  • Go
    • \n
  • Groovy
    • \n
  • haXe
    • \n
  • HTML
    • \n
  • C/C++
    • \n
  • Clojure
    • \n
  • Java
    • \n
  • JavaScript
    • \n
  • JSON
    • \n
  • LaTeX
    • \n
  • LESS
    • \n
  • Liquid
    • \n
  • Lua
    • \n
  • Markdown
    • \n
  • OCaml
    • \n
  • Perl
    • \n
  • pgSQL
    • \n
  • PHP
    • \n
  • Powershell
    • \n
  • Python
    • \n
  • Ruby
    • \n
  • OpenSCAD
    • \n
  • Scala
    • \n
  • SCSS
    • \n
  • SH
    • \n
  • SQL
    • \n
  • SVG
    • \n
  • Text
    • \n
  • Textile
    • \n
  • XML
    • \n
  • XQuery
    • \n
  • YAML
    • \n
\n

We are always adding new themes and new languages to support, so check the menu often! Since we use Ace to provide syntax highlighting, feel free to log an issue there for new requests.

\n\n
" }, { "filename": "uploading_downloading", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Uploading and Downloading Workspace Files", "contents": "\n

Uploading and Downloading Workspace Files

\n

Cloud9 IDE allows you to easily add files to your curent workspace at any time. You can drag and drop files from your computer directly into the Project Files pane, and the IDE will add them to your project. Google Chrome users can also drag entire folders into the IDE.

\n

If a file transfer is halted for some reason--say, if you lose your internet connection--the upload resumes once the connection returns. As the files transfer, the IDE lets you know the current status of the overall transfer, as well as the status of each file being uploaded:

\n

\"Uploading

\n

You can also get an exact copy of your workspace to save on your computer. By going into File > Download Project, you will be provided with a Zip file containing the entirety of your project.

\n\n
" }, + { + "filename": "zen_mode", + "mtime": 1416491265000, + "pageTitle": "Activating Zen Mode", + "contents": "\n

Activating Zen Mode

\n

Note:

this feature is deprecated\n\n
\n
\n\n
\n\n

Zen mode is a full screen coding environment designed to make you more productive. It essentially removes all the additional UI elements in Cloud9 IDE, and places you in a harmonious relationship with your code.

\n

To activate zen mode, simply hover over the upper right corner of the code editor, and click the icon that appears. Keep in mind that you'll need to have a file open before you can launch zen mode. You can resize your window by holding and dragging the left or right border.

\n

To get out of zen mode, hover over the same corner and click the same icon.

\n

You can also enter and exit zen mode via keyboard shortcuts, command line, or from the menu bar at View > Zen Mode.

\n\n
" + }, { "filename": "frameworks_drupal", - "mtime": 1416998221000, + "mtime": 1416491265000, "pageTitle": "Framework: Drupal", "contents": "\n

Framework: Drupal

\n

For Drupal there are some installation guides around which tell you to install PHP first, but that's not necessary with Cloud9.\nYou don't need to install MySQL either, it is already preinstalled in PHP workspaces. \nJust make a new workspace, choose PHP, go to the Terminal, and execute the following:

\n
cd $HOME\ncurl -O http://ftp.drupal.org/files/projects/drupal-7.30.tar.gz\ntar xvf drupal-7.30.tar.gz\nmv drupal-7.30/* workspace/\nmv drupal-7.30/.htaccess workspace/\ncd $HOME/workspace\nmysql-ctl install\nmysql-ctl start\nmysql-ctl status
\n

Open the file install.php in the file tree, and while opened, click on the "Run Project" button in the menu bar on top of the IDE.\nAn URL will be shown at the bottom of the page, something like "https://drupal-c9-lcipriani.c9.io/", but with your username and workspace name in it.

\n

Copy the url in a new browser tab and you will see the install page of Drupal

\n

You can now proceed with the installer

\n

\"Drupal

\n

Now be careful inserting the correct values for the database. You need to change the values as follows:

\n
user: yourusername\ndatabase: c9\nhost: 127.0.0.1
\n

Note:

localhost will not work, while 127.0.0.1 will.\n\n
\n

Open the Advanced Options in the database settings page as shown in the screenshot:

\n

\"Drupal

\n

Now fill the form with the correct site information:

\n

\"Drupal

\n

Continue the setup and enjoy your website!

\n

Note:

if you are not able to load CSS, access your website WITHOUT using https, but use simple http; in another tab open the url: http://drupal-c9-lcipriani.c9.io/\n\n
\n

\"Drupal

\n\n
" }, { - "filename": "git_blame", - "mtime": 1412172002000, - "pageTitle": "Git Blame", - "contents": "\n

Git Blame

\n

Note:

this feature is deprecated\n\n
\n
\n\n
\n\n

When you're working with git repositories, it's helpful to know who made a commit to a particular piece of code. As it turns out, git has a feature called git blame that we've integrated directly into Cloud9 IDE.

\n

By using git blame, you'll be able to instantly discover who edited certain lines of code, when they edited it, and what their commit message at the time was. Clicking on a git commit also highlights other lines of code changed at the same time. To launch the git blame feature, open a file and navigate to Tools > Git > Blame.

\n\n
" + "filename": "frameworks_angularjs", + "mtime": 1416491265000, + "pageTitle": "Framework AngularJS", + "contents": "\n

Framework AngularJS

\n

AngularJS lets you write client-side web \napplications as if you had a smarter browser.

\n

Follow these steps to create an AngularJS application using the official project\ntemplate:

\n
    \n
  1. Create a workspace and choose the PHP workspace type
    2. \n
  2. Open a Terminal, or using the pre-existing one at the bottom
    3. \n
  3. Run the following commands in the Terminal:
    rm -rf * .c9\ngit clone https://github.com/angular/angular-seed.git .\nnpm install\nmv package.json package.json.bak\njq '.scripts.start=\"http-server -a $IP -p $PORT\"' package.json.bak > package.json
    \n
    4. \n
  4. Click the Run Project button in the top menu of the IDE
    5. \n
  5. Check the README.md for further steps
    6. \n
\n

Note:

We are choosing the PHP workspace type to in order to have the Apache runner\nas a default so you can just click Run Project to get started. This doesn't\nlimit the choice of the backend technology you might want to use.
\n\n
" }, { - "filename": "zen_mode", - "mtime": 1412172002000, - "pageTitle": "Activating Zen Mode", - "contents": "\n

Activating Zen Mode

\n

Note:

this feature is deprecated\n\n
\n
\n\n
\n\n

Zen mode is a full screen coding environment designed to make you more productive. It essentially removes all the additional UI elements in Cloud9 IDE, and places you in a harmonious relationship with your code.

\n

To activate zen mode, simply hover over the upper right corner of the code editor, and click the icon that appears. Keep in mind that you'll need to have a file open before you can launch zen mode. You can resize your window by holding and dragging the left or right border.

\n

To get out of zen mode, hover over the same corner and click the same icon.

\n

You can also enter and exit zen mode via keyboard shortcuts, command line, or from the menu bar at View > Zen Mode.

\n\n
" + "filename": "frameworks_express", + "mtime": 1416496691000, + "pageTitle": "Framework: Express", + "contents": "

Framework: Express

\n

Express is a minimal and flexible Node.js web application framework that provides a robust set of features for web and mobile applications.

\n

To get started with an Express app, first create a workspace and choose either the Node.js type, or a Custom workspace type for a clean workspace. Open the new workspace (or an existing one) to follow the instructions below.

\n

Installation

\n

First we'll install the Express project generator and generate an application stub:

\n
$ npm install -g express-generator\n$ express -f .\n$ npm install
\n

You might want to take a look at package.json and update the application name from the default workspace to something more fitting.

\n

Running

\n

Now you have a fully configured express application already. You can run it from the terminal using:

\n
$ bin/www
\n

Now if you click the Preview button in the top menu in the IDE, and choose "Preview with Web Server", this will open the Preview window for your running app.

\n

Creating a Run Configuration

\n

In order to make life easier you can create a run configuration for express.

\n
    \n
  1. Click Run -> Run Configurations -> Manage ...
    2. \n
  2. Click Add New Config
    3. \n
  3. In the run panel fill in Express as name, bin/www as the command and Node 0.10.x as the runner.
    4. \n
  4. You can optionally make this run configuration the default runner by clicking Set As Default. If you do so then clicking the run button will always run the app and not the currently opened file.
    5. \n
\n

The finished run configuration should look something like this

\n

\"Express

\n\n
" + }, + { + "filename": "frameworks_ghost", + "mtime": 1416491265000, + "pageTitle": "Framework: Ghost", + "contents": "\n

Framework: Ghost

\n

Ghost is a simple, powerful publishing platform that \nallows you to share your story with the world.

\n

Create a Ghost blog as follows:

\n
    \n
  1. Create a new workspace (Node.js or Custom for a clean workspace)
    2. \n
  2. Open a Terminal, or use the pre-existing one at the bottom
    3. \n

  3. Run the following commands in the Terminal:

    \n
     $ curl -L https://ghost.org/zip/ghost-latest.zip -o ghost.zip\n $ unzip -uo ghost.zip -d .\n $ rm ghost.zip\n $ npm install --production
    \n
    4. \n

  4. Adapt the config.js file to the Cloud9 environment. Change the following keys:

    \n
     config: {\n     development: {\n         url: 'https://' + process.env.C9_HOSTNAME,\n     },\n     server: {\n         host: process.env.IP,\n         port: process.env.PORT\n     }\n }
    \n
    5. \n

  5. Run Ghost by typing npm start in the console or by opening index.js and\nhitting the run button.

    \n
    6. \n
  6. Click the "Preview" button in the top menu in the IDE, and choose \n"Preview with Web Server". This will open the Preview window for your newly setup Ghost blog
    7. \n
\n

Change the URL to /ghost and create your admin user to login to the Ghost admin interface

\n

Note:

These instructions are based on the official Ghost Installation Guide\n
\n\n
" }, { "filename": "frameworks_ionic", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Framework: Ionic", "contents": "\n

Framework: Ionic

\n

Ionic is an open source front-end framework for developing hybrid mobile apps with HTML5.

\n

Create a Ionic app as follows:

\n
    \n
  1. Create a new workspace (Node.js or Custom for a clean workspace)
    2. \n
  2. Open a Terminal, or use the pre-existing one at the bottom
    3. \n

  3. Run the following commands in the Terminal:

    \n
     $ npm install -g cordova ionic\n $ ionic start myApp sidemenu\n $ cd myApp\n $ ionic serve $PORT
    \n
    4. \n

  4. Click the "Preview" button in the top menu in the IDE, and choose "Preview with Web Server". This will open the Preview window for your running app.

    \n
    5. \n
\n\n
" }, { - "filename": "frameworks_ghost", - "mtime": 1416995769000, - "pageTitle": "Framework: Ghost", - "contents": "\n

Framework: Ghost

\n

Ghost is a simple, powerful publishing platform that \nallows you to share your story with the world.

\n

Create a Ghost blog as follows:

\n
    \n
  1. Create a new workspace (Node.js or Custom for a clean workspace)
    2. \n
  2. Open a Terminal, or use the pre-existing one at the bottom
    3. \n

  3. Run the following commands in the Terminal:

    \n
     $ curl -L https://ghost.org/zip/ghost-latest.zip -o ghost.zip\n $ unzip -uo ghost.zip -d .\n $ rm ghost.zip\n $ npm install --production
    \n
    4. \n

  4. Adapt the config.js file to the Cloud9 environment. Change the following keys:

    \n
     config: {\n     development: {\n         url: 'https://' + process.env.C9_HOSTNAME,\n     },\n     server: {\n         host: process.env.IP,\n         port: process.env.PORT\n     }\n }
    \n
    5. \n

  5. Run Ghost by typing npm start in the console or by opening index.js and\nhitting the run button.

    \n
    6. \n
  6. Click the "Preview" button in the top menu in the IDE, and choose \n"Preview with Web Server". This will open the Preview window for your newly setup Ghost blog
    7. \n
\n

Change the URL to /ghost and create your admin user to login to the Ghost admin interface

\n

Note:

These instructions are based on the official Ghost Installation Guide\n
\n\n
" + "filename": "frameworks_jekyll", + "mtime": 1416491265000, + "pageTitle": "Framework: Jekyll", + "contents": "\n

Framework: Jekyll

\n

Jekyll is a great static site generator, also used by github pages. You simply need to install the Ruby gem and then make sure you pass the right port to the serve command.

\n
$ gem install jekyll\n$ jekyll new my-awesome-site\n$ cd my-awesome-site\n$ jekyll serve --port $PORT
\n\n
" }, { "filename": "frameworks_joomla", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Joomla", "contents": "

Joomla

\n

Joomla is a popular open source CMS. \nInstalling Joomla is very straightforward, but there are just a few quirks to keep in mind, which we describe below.

\n

Note:

all instructions here are based on Joomla v3.x.\n\n
\n

Download Joomla

\n
    \n
  1. Create a Cloud9 workspace of type "Custom" or "PHP"
    2. \n

  2. Download and Unzip Joomla from the Terminal. You can find the latest version on the Joomla website

    \n
     wget http://joomlacode.org/gf/download/frsrelease/19665/160049/Joomla_3.3.3-Stable-Full_Package.zip\n unzip Joomla*.zip\n rm Joomla*.zip
    \n
    3. \n
\n

Start the database

\n

Joomla requires a MySQL database to connect to. MySQL is pre-installed in your workspace, so just execute these commands:

\n
mysql-ctl install\nmysql-ctl start
\n

... and then note the credentials to use in the configuration of Joomla later on.

\n

Install Joomla

\n

To run the Joomla installer, open index.php and run it with the "Run" (or "Run Project") button at the top of the IDE.\nNext, click the URL that's displayed in the Run panel, which looks something like https://joomla-c9-username.c9.io/installation/index.php#. \nThis will open up the Preview window with the installer.

\n

Now, here comes the quirky part: the installer will not work properly if it's loaded over HTTPS, as the Cloud9 Preview window does by default.\nSo, in order to make the Joomla installer work, do the following:

\n
    \n
  1. Pop out the Preview by clicking the Popout icon \"Preview (or copy & load the URL in a browser tab)
    2. \n
  2. Change the URL from https:// to http:// and load it
    3. \n
\n

Now you should be able you to get through the installer successfully.

\n

Main configuration

\n

The main Configuration screen should look like this:

\n

\"Joomla

\n

Enter whatever values you'd like here.

\n

Database

\n

The second quirky and important thing to keep in mind in the Database section, is to use Host Name "0.0.0.0" instead of "localhost".

\n

So use values like shown in the screenshot below:

\n

\"Joomla

\n

Finally

\n

Use whatever settings you'd like in the final installation screen, and after it completes, have Joomla remove the Installation folder for safety.

\n

That's it, you're done and your Joomla setup should run fully on Cloud9!

\n\n
" }, - { - "filename": "revisions", - "mtime": 1412172002000, - "pageTitle": "Revisions", - "contents": "\n

Revisions

\n

Note:

this article is outdated, a new version will follow soon\n\n
\n
\n\n
\n\n

Every time you save a file on Cloud9, a diff of any changes made to it is saved by the server. Over time, you can view these file revisions as content is added and removed from your files. You can also restore a file to any previously saved state; you'll never have to worry about losing your work ever again!

\n

To access file revisions, you can either go to File > File Revisions History, or type Cmd-B on Mac or Ctrl-B on Linux/Windows. This will pop open the Revisions History panel. Red lines indicate lines that were removed; green lines indicate lines that were either added or changed.

\n

At the bottom of the panel, there's a checkbox for showing all of a file's changes. Files changes that occur relatively soon to one another--say, a few seconds--are grouped by the revisions panel as one "change." If you prefer to see every single change as an individual entry, enable the Show all file changes checkbox.

\n

To restore a file to a previous revision, simply click the revisions button for that entry: \"Revisions

\n\n
" - }, { "filename": "frameworks_koa", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Framework: Koa", "contents": "\n

Framework: Koa

\n

Koa is a new web framework designed by the team behind Express, which aims to be a smaller, more expressive, and more robust foundation for web applications and APIs.

\n

To get started with a Koa app, first create a workspace and choose either the Node.js type, or a Custom workspace type for a clean workspace.

\n

Koa.Js makes use of the new generator feature in javascript ECMA 6. \nThis feature is support in Node from 0.11 and up by toggling the --harmony flag. \nBy default Cloud9 runs Node v0.10.x or v0.8.x, depending on your setup, so we first need activate Node version 0.11.x.

\n

Open a Terminal, or using the pre-existing one at the bottom and execute the following in your Terminal:

\n
nvm use 0.11
\n

Next, we need to install Koa itself:

\n
npm install koa
\n

Now we can create a simple Koa.Js server.\nCreate a server.js file in your root folder with this code:

\n
var koa = require('koa');\nvar app = koa();\n\napp.use(function *(){\n    this.body = '<h1>Hello from Koa.Js</h1>';\n});\n\napp.listen(process.env.PORT);
\n

If you now press the Run button on top of the IDE, you will see some errors, as the runner/debugger defaults to 'Node (default)', which is Node version 0.10.x or 0.8.x.

\n

Luckily all you need is to create a Runner file so Cloud9 can run Node 11.x in harmony mode and thereby support generators.

\n

In the Run panel below, click the 'Runner' text input and choose 'New Runner'. \nIn the new Runner file that's opened, save the following code as 'Node 0.11.x.run':

\n
// This file overrides the built-in Node 0.11.x runner\n// For more information see http://docs.c9.io:8080/#!/api/run-method-run\n{\n  \"cmd\": [\n    \"bash\",\n    \"--login\",\n    \"-c\",\n    \"nvm use 0.11 > /dev/null; node --harmony ${debug?--nocrankshaft --nolazy --debug-brk=15454} '$file' $args\"\n  ],\n  \"debugger\": \"v8\",\n  \"debugport\": 15454,\n  \"info\": \"Your code is running at \\\\033[01;34m$url\\\\033[00m.\\n\\\\033[01;31mImportant:\\\\033[00m use \\\\033[01;32mprocess.env.PORT\\\\033[00m as the port and \\\\033[01;32mprocess.env.IP\\\\033[00m as the host in your scripts!\\n\"\n}
\n

Note:

alternatively, you can check 'Show Hidden Files' in your workspace directory tree (the small gear in the upper right corner), and create a new file in the '.c9/runners' folder called 'Node 0.11.x.run' with this code.\n\n
\n

Let's run server.js with this new configuration; in the Run panel on the bottom, choose your new 'Node 0.11.x' Runner, and press Run again.

\n

You Koa.Js server should now be up and running.

\n

Now if you click the Preview button in the top menu in the IDE, and choose "Preview with Web Server", this will open the Preview window for your running app.

\n

(Credits go to Tom at http://kyorcode.blogspot.nl/2014/08/running-koajs-in-cloud9.html)

\n\n
" }, - { - "filename": "frameworks_express", - "mtime": 1416998221000, - "pageTitle": "Framework: Express", - "contents": "

Framework: Express

\n

Express is a minimal and flexible Node.js web application framework that provides a robust set of features for web and mobile applications.

\n

To get started with an Express app, first create a workspace and choose either the Node.js type, or a Custom workspace type for a clean workspace. Open the new workspace (or an existing one) to follow the instructions below.

\n

Installation

\n

First we'll install the Express project generator and generate an application stub:

\n
$ npm install -g express-generator\n$ express -f .\n$ npm install
\n

You might want to take a look at package.json and update the application name from the default workspace to something more fitting.

\n

Running

\n

Now you have a fully configured express application already. You can run it from the terminal using:

\n
$ bin/www
\n

Now if you click the Preview button in the top menu in the IDE, and choose "Preview with Web Server", this will open the Preview window for your running app.

\n

Creating a Run Configuration

\n

In order to make life easier you can create a run configuration for express.

\n
    \n
  1. Click Run -> Run Configurations -> Manage ...
    2. \n
  2. Click Add New Config
    3. \n
  3. In the run panel fill in Express as name, bin/www as the command and Node 0.10.x as the runner.
    4. \n
  4. You can optionally make this run configuration the default runner by clicking Set As Default. If you do so then clicking the run button will always run the app and not the currently opened file.
    5. \n
\n

The finished run configuration should look something like this

\n

\"Express

\n\n
" - }, { "filename": "frameworks_laravel", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Framework: Laravel", "contents": "\n

Framework: Laravel

\n

For Laravel there are some installation guides around which tell you to install PHP first, but that's not necessary with Cloud9.\nJust make a new workspace, choose PHP, go to the Terminal, and execute the following:

\n
rm README.md php.ini hello-world.php\ncomposer create-project laravel/laravel ./laravel --prefer-dist\nshopt -s dotglob\nmv laravel/* ./\nrm -rf laravel
\n

As lavarel is serving its content from the public directory we need to modify the apache config:

\n
sudo vi /etc/apache2/sites-enabled/001-cloud9.conf
\n

Then do the following:

\n
// Change this line\nDocumentRoot /home/ubuntu/workspace\n\n// To following\nDocumentRoot /home/ubuntu/workspace/public
\n

Run the project with the "Run Project" button in the menu bar on top of the IDE.\nIf you click the URL that appears in the Run panel below (in the shape of 'https://laravel-c9-username.c9.io/'), you can preview your new Laravel app.

\n

\"Run

\n\n
" }, { "filename": "frameworks_meteor", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Framework: Meteor", "contents": "\n

Framework: Meteor

\n

Meteor is an open-source platform for building web apps.

\n

Create a Meteor app as follows:

\n
    \n
  1. Create a new workspace (Node.js or Custom for a clean workspace)
    2. \n
  2. Open a Terminal, or using the pre-existing one at the bottom
    3. \n

  3. Run the following commands in the Terminal:

    \n
     curl https://install.meteor.com/ | sh\n meteor create ./my_cool_app\n cd my_cool_app/\n meteor --port $IP:$PORT
    \n
    4. \n

  4. Click the Preview button in the top menu in the IDE, and choose "Preview with Web Server". This will open the Preview window for your running app.

    \n
    5. \n
\n

Note:

Alternatively, for the last step, click on the link that's displayed in the terminal, and change it in the resulting Preview to http://127.0.0.1:8080.
\n\n
" }, { "filename": "frameworks_symfony2", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Framework: Symfony2 ", "contents": "

Framework: Symfony2

\n

Symfony is one of the leading PHP Webframeworks. It is Open-Source and built on top of the Symfony Components.

\n

Getting started

\n
    \n
  1. Create a Cloud9 workspace of the type "Custom" or "PHP"
    2. \n

  2. Install the Intl extension for PHP that is required in most of the Symfony2 projects

    \n
     sudo apt-get install php5-intl
    \n
    3. \n

  3. Set a valid PHP timezone

    \n
     echo 'date.timezone = UTC' | sudo tee --append /etc/php5/apache2/php.ini
    \n
    4. \n

  4. Starting MySQL-Server

    \n
     sudo mysql-ctl install\n sudo mysql-ctl start
    \n
    5. \n
\n

Create a Symfony-Project

\n

Open your Terminal and execute the following to create a new Symfony-Project\nYou need the first line only if you used the PHP Project type for your workspace.

\n
    rm README.md php.ini hello-world.php\n    composer create-project symfony/framework-standard-edition symfony/ \"2.5.*\"\n    mv symfony/{*,.*} ./ \n    rm -rf symfony
\n

The create-project composer command will ask for a few parameters, the only one you need to pay special attention is the database-host parameter.

\n

Running the project

\n

There is a IP address checking in the web/app_dev.php file. To disable this check please remove the following lines

\n
    // This check prevents access to debug front controllers that are deployed by accident to production servers.\n    // Feel free to remove this, extend it, or make something more sophisticated.\n    if (isset($_SERVER['HTTP_CLIENT_IP'])\n        || isset($_SERVER['HTTP_X_FORWARDED_FOR'])\n        || !in_array(@$_SERVER['REMOTE_ADDR'], array('127.0.0.1', 'fe80::1', '::1'))\n    ) {\n        header('HTTP/1.0 403 Forbidden');\n        exit('You are not allowed to access this file. Check '.basename(__FILE__).' for more information.');\n    }
\n

After that add a new run configuration in Menu Run > Run Configurations > New Run Configuration. Select Apache http (PHP, HTML) as a Runner and web/app_dev.php as Command.\nThat's it after you hit Run your server will start up and you can access your new Symfony project.

\n\n
" }, + { + "filename": "create_a_workspace", + "mtime": 1416491265000, + "pageTitle": "Create a Workspace", + "contents": "\n

Create a Workspace

\n

Cloud9 supports three types of workspaces:

\n
    \n
  1. Hosted
    2. \n
  2. FTP
    3. \n
  3. SSH
    4. \n
\n

"Hosted" is the best choice for most people, so in this short "Getting Started" article we'll only describe this option; for other options please read the full Creating a new workspace article.

\n

The first step for creating a new workspace is click the "CREATE NEW WORKSPACE" button in your Dashboard:

\n

\"New

\n

At this point, you'll encounter two choices: Create a new workspace and Clone from URL. \nIn this article we'll only describe the Create a New Workspace option, which allows you to create any of the previously mentioned types of workspaces (hosted, FTP, or SSH).

\n

After clicking on Create a new workspace, you're taken to the screen below:

\n

\"Options

\n

First, let's enter a workspace name.\nDepending on whether you have a Free of Premium account, you can choose to make it either Public (open to anyone with the URL), or Private (only accessible to you and people you share it with).

\n

After this, choose the type of workspace you want to create:

\n\n

Choose the "Hosted" workspace type to start from scratch with a 'Custom' workspace, or simply pick a pre-configured environment like Node.js, WordPress, or Python/Django, and immediately start developing your app.\nThis way you don't need to spend valuable development time on system setup and maintenance, as we maintain it, and you control it.

\n

\"Options

\n

As it's powered by a full Linux Ubuntu environment, hosted workspaces allow you to install any package (sudo apt-get install package), run git commands from the console to push your changes to a GitHub repo or a Bitbucket git repo, etcetera.

\n

Now press Create. That's it! You can now see your new workspace in the dashboard:

\n

\"New

\n

Now, just click Start Editing to get started!

\n

Next up, read how to run an application and set up a database.

\n\n
" + }, { "filename": "run_an_application", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Run an application", "contents": "

Run an application

\n

On Hosted and SSH workspaces, Cloud9 provides two ways to run your application:

\n
    \n
  1. Using the Run panel with built-in Runners for many languages
    2. \n
  2. From a Terminal
    3. \n
\n

Method 1: Use the Run panel

\n

First, open the file you want to run.

\n

Next, click on the Run button in the top menu bar in the IDE.

\n

\"Run

\n

The Run button acts as a sort of shortcut to the Run panel, which will appear by default in the bottom of the IDE when you run a file.\nThis automatically runs the currently active file, and it will guess which Runner to use based on the extension of the file.

\n

When you're ready to stop your app, click on the Stop Button button in the menu bar at any time, or from the Run panel below.

\n

\"Run

\n

On the Run panel, you'll notice a few more options you can set. \nFilling these textboxes out creates a Run Configuration.

\n
    \n
  • Name: the name of your run scenario
    • \n
  • Command: the command you want to run; this is usually the location of your running file in your project, but it also allows you to provide any additional command line arguments you want to pass to your app
    • \n
  • Runner: defines how you want your code to be run. A wide range of Runners is available by default, from Apache to Node.js and Shell scripts, and you can define your own.
    • \n
  • CWD: Set the current working directory to start from
    • \n
  • Environment: Set environment variables
    • \n
  • \n
\n

Tip:

If you can't find the Runner you need from the default set, you can create your own custom Runner.\n\n
\n

For some default runners like Node.js, it's an option to Run in debug mode, which indicates that you want to run the current code through the debugger. \nThis will reveal (or collapse) the debugging tools panel described in Running and Debugging your code.

\n

Method 2: From the Terminal

\n

The built-in Terminal provides access to all underlying system commands, including your Runners such as Node.js. \nSimply open up a Terminal from the "+" sign, or use CMD+T (Mac) / Control+T (Windows), and then execute the command you need to run your app, e.g. node server.js.

\n

(Pre-)View your application

\n

To find out where your application is running you can do two things:

\n
    \n
  1. Use the Preview button on the top to preview one of your files. The URL in the browser bar in the Preview can also be used in any browser tab/window.
    2. \n
  2. Use the Share button on the top to figure out the URLs of running Application and the Preview. The Editor URL is only used to share your entire Cloud9 workspace to collaborate on code.
    3. \n
\n

Tip:

If you can't find how to preview your running app, try to use port 8080 in the URL.
\n\n
" }, { "filename": "setup_a_database", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Set up a database", "contents": "

Set up a database

\n

MySQL

\n

From the Terminal, run the following command:

\n
$ mysql-ctl install
\n

The output will be:

\n
MySQL 5.5 database added.  Please make note of these credentials:\n\nRoot User: username\nDatabase Name: c9
\n

Now you can connect to the database using the ip 127.0.0.1 and the default port 3306.\nYou can also test it using our tool from the Terminal:

\n
$ mysql-ctl cli\nWelcome to the MySQL monitor.  Commands end with ; or \\g.\nYour MySQL connection id is 24\nServer version: 5.5.37-0ubuntu0.14.04.1 (Ubuntu)\n\nCopyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved.\n\nOracle is a registered trademark of Oracle Corporation and/or its\naffiliates. Other names may be trademarks of their respective\nowners.\n\nType 'help;' or '\\h' for help. Type '\\c' to clear the current input statement.\n\nmysql>  show databases;\n+--------------------+\n| Database           |\n+--------------------+\n| information_schema |\n| c9                 |\n| mysql              |\n| performance_schema |\n+--------------------+\n4 rows in set (0.15 sec)
\n

MongoDB

\n

From the Terminal, run the following command:

\n
$ mongod --bind_ip=$IP --nojournal
\n

The output will include:

\n
...\nwaiting for connections on port 27017
\n

Now you can open the mongo shell in a new Terminal, running following command:

\n
$ mongo
\n

To stop the MongoDB instance press Control+C in the Terminal where mongod is running.\nNow have a look at the currently used database:

\n
$ mongo\nmongo> db\ntest
\n\n
" }, - { - "filename": "dashboard", - "mtime": 1412172002000, - "pageTitle": "The Dashboard", - "contents": "\n

The Dashboard

\n

After you have logged into Cloud9, you are placed into your account's dashboard. From here, you can edit your profile and manage workspaces you have access to.

\n

\"An

\n

In the top-left corner of the dashboard, your username is displayed. Within the user context, you can view your user profile by clicking on Your Account:

\n

\"A

\n

The user profile contains:

\n
    \n
  • Your recent activities, including a list of actions you have recently performed, such as cloning, opening, and deleting projects
    • \n
  • Your add-on services, which you've integrated into Cloud9. Currently, these are GitHub and Bitbucket.
    • \n
  • Your account settings, where you're given the following choices:
      \n
    • Change your password
      • \n
    • Show your SSH key
      • \n
    • Upgrade to premium (or, downgrade from it)
      • \n
    • Delete your account
      • \n
    \n
    • \n
\n

The gravatar that is used for your profile is handled by gravatar.com. If you don't have a gravatar yet, Cloud9 IDE uses an uninspiring default.

\n

In the left panel, you'll find a list of various projects associated with your account. These are:

\n
    \n
  • My Projects: these are projects you've created or cloned, and own
    • \n
  • Shared With Me: these are projects shared with you by other Cloud9 users
    • \n
  • Recently Visited: these are projects you've seen lately
    • \n
  • Projects on GitHub: a list of your uncloned public and private GitHub projects
    • \n
  • Projects on Bitbucket: a list of your uncloned public and private Bitbucket projects
    • \n
\n

Clicking on the \"Project next to MY PROJECTS lets you:

\n
    \n
  • Create a new project
    • \n
  • Clone from URL
    • \n
\n

\"Creating

\n

For more information on creating new workspaces, see this section of the documentation.

\n

You can always filter your project list by entering text in the text bar to find matching projects. If you need to update the list, click the refresh icon at the bottom of the panel: \"Refresh

\n\n
" - }, - { - "filename": "create_a_workspace", - "mtime": 1412172002000, - "pageTitle": "Create a Workspace", - "contents": "\n

Create a Workspace

\n

Cloud9 supports three types of workspaces:

\n
    \n
  1. Hosted
    2. \n
  2. FTP
    3. \n
  3. SSH
    4. \n
\n

"Hosted" is the best choice for most people, so in this short "Getting Started" article we'll only describe this option; for other options please read the full Creating a new workspace article.

\n

The first step for creating a new workspace is click the "CREATE NEW WORKSPACE" button in your Dashboard:

\n

\"New

\n

At this point, you'll encounter two choices: Create a new workspace and Clone from URL. \nIn this article we'll only describe the Create a New Workspace option, which allows you to create any of the previously mentioned types of workspaces (hosted, FTP, or SSH).

\n

After clicking on Create a new workspace, you're taken to the screen below:

\n

\"Options

\n

First, let's enter a workspace name.\nDepending on whether you have a Free of Premium account, you can choose to make it either Public (open to anyone with the URL), or Private (only accessible to you and people you share it with).

\n

After this, choose the type of workspace you want to create:

\n\n

Choose the "Hosted" workspace type to start from scratch with a 'Custom' workspace, or simply pick a pre-configured environment like Node.js, WordPress, or Python/Django, and immediately start developing your app.\nThis way you don't need to spend valuable development time on system setup and maintenance, as we maintain it, and you control it.

\n

\"Options

\n

As it's powered by a full Linux Ubuntu environment, hosted workspaces allow you to install any package (sudo apt-get install package), run git commands from the console to push your changes to a GitHub repo or a Bitbucket git repo, etcetera.

\n

Now press Create. That's it! You can now see your new workspace in the dashboard:

\n

\"New

\n

Now, just click Start Editing to get started!

\n

Next up, read how to run an application and set up a database.

\n\n
" - }, - { - "filename": "ide_overview", - "mtime": 1412172002000, - "pageTitle": "IDE Overview", - "contents": "

IDE Overview

\n

Note:

this article is outdated, a new version will follow soon\n\n
\n

Cloud9 IDE can be thought of as being divided into the following components:

\n

\"IDE

\n

Throughout the documentation, we'll refer to these sections by name. We can identify several distinct areas in the editor:

\n
    \n
  • The top menu bar is the uppermost area, with easy access to a variety of menus
    • \n
  • The project bar on the left lets you manipulate various aspects of your project, including its active files, preferences, and choices for deployment
    • \n
  • The panel displays views according to what's been selected in the project bar
    • \n
  • The toolbar is on the far right, where you can find tools used when debugging your code. Projects that are open with collaboration also make use of this panel for chatting.
    • \n
  • The code editor is the main area where you write your code.
    • \n
  • The console is the bottom area of the window. It's an expandable area that can act like a desktop terminal to enter command line input (like ls or mkdir). It also displays output provided by your program's print statements (like console.log()), as well as providing an area for search results
    • \n
\n

The Project Bar, Tool Bar, and Console are powerful features, so their documentation is provided separately. We'll talk about the rest of the editor below:

\n

Remember: nearly every UI element can be collapsed, in order to provided a more harmonious coding experience. For example, clicking on the buttons in the upper left of the editor allows you to hide the panels and top menu bar:
\"Hiding

\n

The Top Menu Bar

\n

\"A

\n

In this section, you can find the usual menus for creating and saving files, changing your view, applying a new theme for the editor, and switching between windows.

\n

In the middle of the menu bar you'll find the debug button: \"The. This is used for running and debugging your code. For more information, see the section on "Running and Debugging Your Code"..

\n

\n

The preview button \"The provides you with a look of what the currently active file would look like in the browser. For text files, this is usually just the raw text, but certain files, like HTML or XML, render as the actual markup.

\n

The autosave button indicates the status of your current saves: \"Autosave. Files are saved automatically by Cloud9 IDE, and every revision is made available for you to browse through. For more information, see the section on revisions and saving.

\n

On the far right of the menu, near the Cloud9 IDE logo, there are two more icons: one to return to the dashboard, and one to return to the Cloud9 IDE homepage.

\n

The Code Editor

\n

This is where most of the action happens. Every file you open appears here as a tab. You can open a new file easily by clicking on the \"Tab button to the right of the last tab. Cloud9 IDE offers syntax highlighting for over two dozen programming languages.

\n

The code editor supports a large number of keyboard shortcuts to increase your productivity. For an up-to-date list of these within the IDE, simply go to Help > Keyboard Shortcuts.

\n

If you hover over to the upper-right corner, you can activate zen-mode, which is a full screen coding environment.

\n

At the lower-right corner, you can find the status bar.

\n\n
" - }, { "filename": "share_a_workspace", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Share a workspace", "contents": "

Share a workspace

\n

As you develop your application, often you just want to quickly demo your work-in-progress to a colleague, customer, or friend. \nOr you want to pull in a fellow dev to debug an issue, or to pair program.

\n

Cloud9 enables you to do just these things, easily: share your entire development environment, the running application, or just a preview of your running application. \nHere we describe how to access these options, and how to use each.

\n

Share dialog

\n

The best place to start sharing is from the dedicated "Share" dialog. \nAccess it via the "Share" button on the right top of the IDE, or via the menu in Window > Share...

\n

\"Share

\n

Here's what you see when you pull up the Share dialog:

\n

\"Share

\n

Links to share

\n
    \n
  • Editor: see section "Share your development environment"
    • \n
  • Application: see section "Share your application"
    • \n
  • \n
\n

If you enable the "Public" checkbox for an option, it will make the URL accessible for anyone with the URL.\nFor public workspaces all these URLs are public by default, but for private workspaces you have to enable them manually.

\n

Who has access

\n

This section refers to people you have specifically granted access to your entire development environment.\n(R) gives Read access only to that person: the ability to open and view files, and to run your code.\n(RW) or "Read/Write" also gives that person the ability to write to files.

\n

Invite people

\n

This section enables you to invite people to your workspace and immediately set if they have just "Read" or "Read+Write" rights. \nYou can invite people by their email address or Cloud9 username. \nYou can also choose whether or not send an automatic email to that person that they've been invited to your workspace.

\n

Share your development environment

\n

Cloud9's Collaboration features allow you to share your entire development environment so you can work on code together, much like working on a document in Google Docs.\nYou'll actually be able to see each other's cursor as you type, run your app, share the Terminal(s), and talk in the group chat.\nSee the screenshot below for what this looks like:

\n

\"Collaboration

\n

In order to share your entire development environment, do one of the following:

\n
    \n
  1. Make the URL publicly available to everyone: check the "Public" checkbox for the "Editor" in the "Links to Share" section.
    2. \n
  2. Choose to share only with specific people: invite them from the "Invite people" section.
    3. \n
  3. Grant/revoke access rights in the "Who has access" section.
    4. \n
\n

If someone asks for either Read or Read+Write access to your workspace, you can accept or deny them from the Collaboration panel on the right.

\n

Note:

alternatively you can just share the URL to your workspace from the browser's URL bar and accept members as they request access to your workspace\n\n
\n

Share your application

\n

If you Run your application the result can be shared by copying the URL from the dialog. \nThis URL can only be viewed if it's made Public by checking the "Public" checkbox next to the "Application" in the "Links to share" section.

\n

People who have full read access to your workspace (as defined in the "Who has access") can view this URL whether it's public or not.

\n

Note:

alternatively you can just share the URL to your running app from the Preview panels' URL bar\n\n
\n

Share a Preview

\n

If you Preview a file in your application, it can be shared by copying the URL from the dialog. \nThis URL can only be viewed if it's made Public by checking the "Public" checkbox next to the "Preview" in the "Links to share" section.

\n

People who have full read access to your workspace (as defined in the "Who has access") can view this URL whether it's public or not.

\n

Note:

alternatively you can just share the URL to your Preview from the Preview panels' URL bar\n\n
\n

Tip:

If you can't find how to preview your running app, try to use port 8080 in the URL.
\n\n
" }, { "filename": "console", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "The Console", "contents": "

The Console

\n

Note:

this feature is deprecated\n\n
\n

The Console is at the bottom of the IDE. It's where you can enter command line input, view output from your program, and push and pull your files between your code repositories.

\n

Note:

The Console contains a full-fledged terminal, which provides you with a TTY interface for direct access to the machine that Cloud9 is running on.\n\n
\n

Available Commands

\n

The terminal can perform all Unix commands, and allows for path autocompletion by hitting Tab.

\n

For instance, you can use mercurial commands (hg) and git commands (git) to communicate with the system, and to push your code between repositories. Typing hg or git shows the complete list of commands that are available for these services. For more information about these commands, please check their respective documentation:

\n\n

To use mercurial commands on the project you are working on, you must have a mercurial project set up; the same holds true for git. Follow these links to learn more about how to set up these project in Cloud9:

\n\n

Output

\n

The output tab in the Console shows information whenever a user is running or debugging a program. The content is similar to the output of a desktop terminal:
\"Screenshot

\n

The output tab also displays the error and additional information that can improve your coding quality. You can use the Console to output results from your running application, just like a regular terminal.

\n

As your process runs, you'll see a message similar to this one indicating that Cloud9 is running something in the background: \"Running

\n

If you hover over this message, you can opt to cancel the process by clicking on the button: \"Cancelling

\n\n
" }, { - "filename": "frameworks_angularjs", - "mtime": 1412172002000, - "pageTitle": "Framework AngularJS", - "contents": "\n

Framework AngularJS

\n

AngularJS lets you write client-side web \napplications as if you had a smarter browser.

\n

Follow these steps to create an AngularJS application using the official project\ntemplate:

\n
    \n
  1. Create a workspace and choose the PHP workspace type
    2. \n
  2. Open a Terminal, or using the pre-existing one at the bottom
    3. \n
  3. Run the following commands in the Terminal:
    rm -rf * .c9\ngit clone https://github.com/angular/angular-seed.git .\nnpm install\nmv package.json package.json.bak\njq '.scripts.start=\"http-server -a $IP -p $PORT\"' package.json.bak > package.json
    \n
    4. \n
  4. Click the Run Project button in the top menu of the IDE
    5. \n
  5. Check the README.md for further steps
    6. \n
\n

Note:

We are choosing the PHP workspace type to in order to have the Apache runner\nas a default so you can just click Run Project to get started. This doesn't\nlimit the choice of the backend technology you might want to use.
\n\n
" + "filename": "dashboard", + "mtime": 1416491265000, + "pageTitle": "The Dashboard", + "contents": "\n

The Dashboard

\n

After you have logged into Cloud9, you are placed into your account's dashboard. From here, you can edit your profile and manage workspaces you have access to.

\n

\"An

\n

In the top-left corner of the dashboard, your username is displayed. Within the user context, you can view your user profile by clicking on Your Account:

\n

\"A

\n

The user profile contains:

\n
    \n
  • Your recent activities, including a list of actions you have recently performed, such as cloning, opening, and deleting projects
    • \n
  • Your add-on services, which you've integrated into Cloud9. Currently, these are GitHub and Bitbucket.
    • \n
  • Your account settings, where you're given the following choices:
      \n
    • Change your password
      • \n
    • Show your SSH key
      • \n
    • Upgrade to premium (or, downgrade from it)
      • \n
    • Delete your account
      • \n
    \n
    • \n
\n

The gravatar that is used for your profile is handled by gravatar.com. If you don't have a gravatar yet, Cloud9 IDE uses an uninspiring default.

\n

In the left panel, you'll find a list of various projects associated with your account. These are:

\n
    \n
  • My Projects: these are projects you've created or cloned, and own
    • \n
  • Shared With Me: these are projects shared with you by other Cloud9 users
    • \n
  • Recently Visited: these are projects you've seen lately
    • \n
  • Projects on GitHub: a list of your uncloned public and private GitHub projects
    • \n
  • Projects on Bitbucket: a list of your uncloned public and private Bitbucket projects
    • \n
\n

Clicking on the \"Project next to MY PROJECTS lets you:

\n
    \n
  • Create a new project
    • \n
  • Clone from URL
    • \n
\n

\"Creating

\n

For more information on creating new workspaces, see this section of the documentation.

\n

You can always filter your project list by entering text in the text bar to find matching projects. If you need to update the list, click the refresh icon at the bottom of the panel: \"Refresh

\n\n
" + }, + { + "filename": "ide_overview", + "mtime": 1416491265000, + "pageTitle": "IDE Overview", + "contents": "

IDE Overview

\n

Note:

this article is outdated, a new version will follow soon\n\n
\n

Cloud9 IDE can be thought of as being divided into the following components:

\n

\"IDE

\n

Throughout the documentation, we'll refer to these sections by name. We can identify several distinct areas in the editor:

\n
    \n
  • The top menu bar is the uppermost area, with easy access to a variety of menus
    • \n
  • The project bar on the left lets you manipulate various aspects of your project, including its active files, preferences, and choices for deployment
    • \n
  • The panel displays views according to what's been selected in the project bar
    • \n
  • The toolbar is on the far right, where you can find tools used when debugging your code. Projects that are open with collaboration also make use of this panel for chatting.
    • \n
  • The code editor is the main area where you write your code.
    • \n
  • The console is the bottom area of the window. It's an expandable area that can act like a desktop terminal to enter command line input (like ls or mkdir). It also displays output provided by your program's print statements (like console.log()), as well as providing an area for search results
    • \n
\n

The Project Bar, Tool Bar, and Console are powerful features, so their documentation is provided separately. We'll talk about the rest of the editor below:

\n

Remember: nearly every UI element can be collapsed, in order to provided a more harmonious coding experience. For example, clicking on the buttons in the upper left of the editor allows you to hide the panels and top menu bar:
\"Hiding

\n

The Top Menu Bar

\n

\"A

\n

In this section, you can find the usual menus for creating and saving files, changing your view, applying a new theme for the editor, and switching between windows.

\n

In the middle of the menu bar you'll find the debug button: \"The. This is used for running and debugging your code. For more information, see the section on "Running and Debugging Your Code"..

\n

\n

The preview button \"The provides you with a look of what the currently active file would look like in the browser. For text files, this is usually just the raw text, but certain files, like HTML or XML, render as the actual markup.

\n

The autosave button indicates the status of your current saves: \"Autosave. Files are saved automatically by Cloud9 IDE, and every revision is made available for you to browse through. For more information, see the section on revisions and saving.

\n

On the far right of the menu, near the Cloud9 IDE logo, there are two more icons: one to return to the dashboard, and one to return to the Cloud9 IDE homepage.

\n

The Code Editor

\n

This is where most of the action happens. Every file you open appears here as a tab. You can open a new file easily by clicking on the \"Tab button to the right of the last tab. Cloud9 IDE offers syntax highlighting for over two dozen programming languages.

\n

The code editor supports a large number of keyboard shortcuts to increase your productivity. For an up-to-date list of these within the IDE, simply go to Help > Keyboard Shortcuts.

\n

If you hover over to the upper-right corner, you can activate zen-mode, which is a full screen coding environment.

\n

At the lower-right corner, you can find the status bar.

\n\n
" + }, + { + "filename": "ide_preferences", + "mtime": 1416491265000, + "pageTitle": "IDE Preferences", + "contents": "

IDE Preferences

\n

Note:

this article is outdated, a new version will follow soon\n\n
\n

There are many different ways to configure the IDE. Below is a list of the options available, and what they do.

\n

Note:

All of these options are on a per-project basis. Changing them in one project does not affect any another.\n\n
\n

General

\n

This section controls the overall IDE behavior:

\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
Preference NameDescription
Enable UI AnimationsEnables or disables fluid animations for various UI elements, such as the Project Bar
Animate ScrollingEnables or disables fluid animations when scrolling through code (such as for goto line)
Enable Auto-SaveIf enabled, automatically saves your files on every change
On Save, Strip WhitespaceWhen saving a file, you can remove all extraneous whitespace from your code lines
Reveal Active File in Project TreeEnabling this jumps the project tree to the active file whenever a tab changes to a different file
Warn Before ExitingPrevents accidental data loss by showing a dialog asking if you really want to leave Cloud9 IDE when closing your browser
Node.js RuntimeDefines the default runtime for your Node.js code. "Auto" is based on whatever is in the package.json file, while "Default" reverts to Node 0.6.x.
KeybindingsAllows you to choose which operating system to use for keyboard shortcuts
\n

Language Support

\n

This section controls language analysis options:

\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
\n \n \n \n \n \n \n \n
Preference NameDescription
Enable Hints and Warnings RulesPresents information about your code in the gutter
Highlight Variable InstancesHighlights variable instances in your code
Mark Undeclared VariablesProvides warnings if a variable is being used and has not been declared yet
Mark Unused Function ArgumentsProvides a strikethrough for arguments in a function that are not being used
Warning LevelSpecifies the minimum level of information severity you want provided in the gutter
\n

Code Editor

\n

This section controls language analysis options:

\n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
Preference NameDescription
Auto-pair Quotes, Brackets, etc.When enabled, typing ", (, or [ will actually make two characters appear. In addition, whenever you highlight a word and type one of these characters, it is surrounded by that character (e.g. words becomes "words")
Full Line SelectionWhen highlighting lines, this option will highlight all ending whitespace, until the end of the editor window
Highlight Active LinePresents a darker shade in the code editor to indicate which line you're currently on
Highlight Gutter LinePresents a darker shade in the gutter which line you're currently on
Show Invisible CharactersShows invisibles characters in the editor, like tabs and line breaks
Show Indent GuidesShows the indent guides in the editor, letting you see your code's nestings
Show GutterShows the gutter in the editor, which indicates line numbers, warnings, and errors
Highlight Selected WordIf you highlight a word, this highlights all matching words in the editor
Auto-hide Horizontal ScrollWhen this is enabled, this will hide the horizontal scroll bar in the editor. Note that this has no effect in Mac OS X 10.7 (Lion) and above, since all scrollbars, by default, auto-hide.
Vim ModeWhen enabled, allows you to use vim keybindings in the IDE
Code FoldingWhen enabled, allows you to show or hide "blocks" of code
Fade Fold WidgetsWhen enabled, fades the folding widgets in the gutter
Font SizeChanges the font size of the code in the editor
Show Print MarginShows (and defines) the number of characters possible in line, before it wraps
Soft TabsIndicates how many spaces a single tab represents
Mouse Scroll SpeedDefines the speed of the mouse scrolls
Newline ModeSpecifies the newline mode for the IDE
\n

Terminal

\n

This section controls the behavior for the terminal:

\n
\n \n \n \n \n \n \n \n
\n \n \n \n \n \n \n \n \n \n \n
\n \n \n \n
Preference NameDescription
ScrollbackSets the scrollback buffer for the terminal
Font FamilySets the font for the terminal
Font SizeSets the font size for the terminal
Blinking CursorSpecifies whether or not you want the cursor to blink
\n

Code Tools

\n

This section controls the various tools that are available in the IDE:

\n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n
Preference NameDescription
Enable Color PickerMakes the color picker available for use
Preserve Empty LinesWhen enabled, the editor keeps any new lines without text
Keep Array IndentionWhen enabled, tabs and newlines in arrays are preserved. For example, the follow array would remain as-is with this option:\n 
\n        var o = [{\n            a: b\n        }, {\n            c: d\n        }];\n
\n
JSLint Strict WhitespaceIf selected, all brackets are preceded by a space. For example, if(x){ becomes if (x) {, and function(arg){ becomes function (arg) {
BracesThese options control how braces are handled in the IDE:\n
    \n
  • Braces with control statement: braces are left "in-line" alongside the code statements. For example, code is formatted like this:\n 
    \n    if (true) {\n        var x = 3;\n    } else {\n        var x = 5;\n    }\n
    \n
    • \n
  • Braces on own line: braces are always placed on their own line. For example, code is formatted like this:\n 
    \n    if (true)\n    {\n        var x = 3;\n    } else\n    {\n        var x = 5;\n    }\n
    \n
    • \n
  • End braces on own line: only the ending braces have their own line. For example, code is formatted like this:\n 
    \n    if (true) {\n        var x = 3;\n    }\n    else {\n        var x = 5;\n    }\n
    \n
    • \n
\n
\n
" }, { "filename": "keybindings", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Commands and Keybindings", "contents": "\n

Commands and Keybindings

\n

Note:

this article is outdated, a new version will follow soon\n\n
\n

Nearly every action in Cloud9 has a corresponding command associated with it. On top of that, every command also has a keybinding that can be used to effortlessly execute the command.

\n

Below is a list of every single command and keybinding used by Cloud9. Have fun being efficient!

\n
\n \n
\n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
Command NameKeybinding
Abortclicommand˄-C
AddCursorAbove˄-⌥-Up
AddCursorAboveSkipCurrent˄-⌥-⇧-Up
AddCursorBelow˄-⌥-Down
AddCursorBelowSkipCurrent˄-⌥-⇧-Down
Backspace˄-⌫
Beautify⌘-⇧-B
Clearcut⎋
Closeallbutme⌥-˄-W
Closealltabs⌥-⇧-W
Closetab⌥-W
Complete˄-Space
Copy⌘-C
Copylinesdown⌘-⌥-Down
Copylinesup⌘-⌥-Up
Cut⌘-X
DelDelete
DuplicateSelection⌘-⇧-D
Escapeconsole⎋
EvalInteractive⌘-Return
Find⌘-F
Findnext⌘-G
Findprevious⌘-⇧-G
Fold⌘-⌥-L
Foldall⌘-⌥-0
GolinedownDown
GolineupUp
Gotoend⌘-End
Gotofile⌘-E
GotoleftLeft
Gotoline⌘-L
Gotolineend⌘-Right
Gotolinestart⌘-Left
GotopagedownPageDown
GotorightRight
Gotostart⌘-Home
Gototableft⌘-[
Gototabright⌘-]
Gotowordleft⌥-Left
Gotowordright⌥-Right
IndentTab
Jumptomatching˄-⇧-P
Largerfont˄-⇧-.
Movelinesdown⌥-Down
Movelinesup⌥-Up
Movetableft⌘-⌥-[
Movetabright⌘-⌥-]
Newfile⌥-⇧-N
Newfiletemplate⌥-˄-N
Newfolder⌥-˄-⇧-N
Nexttab⌥-Tab
Openfilepanel⇧-⌘-U
Opensettingspanel⌘-,
Opentreepanel⌘-U
Outdent⇧-Tab
Outline⌘-⇧-E
Paste⌘-V
Previoustab⌥-⇧-Tab
Quicksave⌘-S
Quickwatch⌥-Q
Redo⌘-⇧-Z
Removeline⌘-D
Removetolineend˄-K
Removetolinestart⌘-⌫
Removewordleft⌥-⌫
Removewordright⌥-Delete
RenameVar⌥-⌘-R
Replace⌥-⌘-F
Replaymacro⌘-˄-R
ResumeF8
Revealtab⇧-⌘-L
Reverttosaved˄-⇧-Q
Revisionpanel⌘-B
RunF5
Saveas⌘-⇧-S
Savetabsession⇧-˄-S
Searchinfiles⇧-⌘-F
SelectMoreAfter˄-⌥-Right
SelectMoreBefore˄-⌥-Left
SelectNextAfter˄-⌥-⇧-Right
SelectNextBefore˄-⌥-⇧-Left
Selectall⌘-A
Selectdown⇧-Down
Selectleft⇧-Left
Selectright⇧-Right
Selecttoend⌘-⇧-Down
Selecttolineend⌘-⇧-Right
Selecttolinestart⌘-⇧-Left
Selecttostart⌘-⇧-Up
Selectup⇧-Up
Selectwordleft⌥-⇧-Left
Selectwordright⌥-⇧-Right
Smallerfont˄-⇧-,
SplitIntoLines˄-⇧-L
StepintoF11
Stepout⇧-F11
StepoverF10
Stop⇧-F5
Switchconsole⇧-⎋
Tab0⌘-0
Tab1⌘-1
Tab2⌘-2
Tab3⌘-3
Tab4⌘-4
Tab5⌘-5
Tab6⌘-6
Tab7⌘-7
Tab8⌘-8
Tab9⌘-9
ToggleTabs˄-M
Togglecomment⌘-/
Toggleconsole˄-⎋
Togglerecording⌘-⇧-R
Tolowercase˄-⇧-U
Touppercase˄-U
Transposeletters˄-T
Undo⌘-Z
Unfold⌘-⌥-⇧-L
Unfoldall⌘-⌥-⇧-0
Zen⌥-Z
Zenslow⇧-⌥-Z
\n
\n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
Command NameKeybinding
AbortclicommandCtrl-C
AddCursorAboveCtrl-Alt-Up
AddCursorAboveSkipCurrentCtrl-Alt-Shift-Up
AddCursorBelowCtrl-Alt-Down
AddCursorBelowSkipCurrentCtrl-Alt-Shift-Down
BackspaceCommand-Backspace
BeautifyShift-Ctrl-B
ClearcutESC
CloseallbutmeCtrl-Alt-W
ClosealltabsCtrl-Shift-W
ClosetabCtrl-W
CompleteCtrl-Space
CopyCtrl-C
CopylinesdownAlt-Shift-Down
CopylinesupAlt-Shift-Up
CutCtrl-X
DelDelete
DuplicateSelectionCtrl-Shift-D
EscapeconsoleEsc
EvalInteractiveCtrl-Return
FindCtrl-F
FindnextCtrl-K
FindpreviousCtrl-Shift-K
FoldAlt-L
FoldallAlt-0
GolinedownDown
GolineupUp
GotoendCtrl-End
GotofileCtrl-E
GotoleftLeft
GotolineCtrl-G
GotolineendAlt-Right
GotolinestartAlt-Left
GotopagedownPageDown
GotorightRight
GotostartCtrl-Home
GototableftCtrl-[
GototabrightCtrl-]
GotowordleftCtrl-Left
GotowordrightCtrl-Right
IndentTab
JumptomatchingCtrl-P
LargerfontCtrl-Shift-.
MovelinesdownAlt-Down
MovelinesupAlt-Up
MovetableftCtrl-Alt[
MovetabrightCtrl-Alt-]
NewfileCtrl-N
NewfiletemplateCtrl-Alt-N
NewfolderCtrl-N
NexttabCtrl-Tab
OpenfilepanelShift-Ctrl-U
OpensettingspanelCtrl-,
OpentreepanelCtrl-U
OutdentShift-Tab
OutlineCtrl-Shift-E
PasteCtrl-V
PrevioustabCtrl-Shift-Tab
QuicksaveCtrl-S
QuickwatchAlt-Q
RedoCtrl-Shift-Z
RemovelineCtrl-D
RemovetolineendAlt-Delete
RemovetolinestartAlt-Backspace
RemovewordleftCtrl-Backspace
RemovewordrightCtrl-Delete
RenameVarCtrl-Alt-R
ReplaceAlt-Shift-F
ReplaymacroAlt-R
ResumeF8
RevealtabCtrl-Shift-L
ReverttosavedCtrl-Shift-Q
RevisionpanelCtrl-B
RunF5
SaveasCtrl-Shift-S
SavetabsessionShift-Ctrl-S
SearchinfilesCtrl-Shift-F
SelectMoreAfterCtrl-Alt-Right
SelectMoreBeforeCtrl-Alt-Left
SelectNextAfterCtrl-Alt-Shift-Right
SelectNextBeforeCtrl-Alt-Shift-Left
SelectallCtrl-A
SelectdownShift-Down
SelectleftShift-Left
SelectrightShift-Right
SelecttoendCtrl-Shift-End
SelecttolineendAlt-Shift-Right
SelecttolinestartAlt-Shift-Left
SelecttostartCtrl-Shift-Home
SelectupShift-Up
SelectwordleftCtrl-Shift-Left
SelectwordrightCtrl-Shift-Right
SmallerfontCtrl-Shift-,
SplitIntoLinesCtrl-Shift-L
StepintoF11
StepoutShift-F11
StepoverF10
StopShift-F5
SwitchconsoleShift-Esc
Tab0Ctrl-0
Tab1Ctrl-1
Tab2Ctrl-2
Tab3Ctrl-3
Tab4Ctrl-4
Tab5Ctrl-5
Tab6Ctrl-6
Tab7Ctrl-7
Tab8Ctrl-8
Tab9Ctrl-9
ToggleTabsCtrl-M
TogglecommentCtrl-/
ToggleconsoleF6
TogglerecordingAlt-Shift-R
TolowercaseCtrl-Shift-U
TouppercaseCtrl-U
TransposelettersCtrl-T
UndoCtrl-Z
UnfoldAlt-Shift-L
UnfoldallAlt-Shift-0
ZenAlt-Z
ZenslowShift-Alt-Z
\n
\n
\n
\n
" }, { - "filename": "the_editor", - "mtime": 1412172002000, - "pageTitle": "The Editor", - "contents": "\n

The Editor

\n

The editor is the most important element of any IDE; that's why Cloud9 developed ACE. ACE is a high-performance code editor for the web that supports over 40 different languages, over two dozen themes, and can still work faithfully on large documents (at last count, four million lines of code was the upper limit). It also contains a bevy of features you'd expect from traditional desktop editors. Among these include:

\n
    \n
  • Undo and Redo support
    • \n
  • Cut, Copy, and Paste functionality
    • \n
  • Line manipulation, including:
      \n
    • Indenting and outdenting
      • \n
    • Moving and copying lines up or down
      • \n
    • Removing lines from any point
      • \n
    • Splitting lines
      • \n
    \n
    • \n
  • Highlighting and commenting blocks of code
    • \n
  • Removing words to the right or the left
    • \n
  • Transposing letters
    • \n
  • Code folding (including the entire file)
    • \n
  • Converting cases
    • \n
  • Multiple cursors
    • \n
  • Autocompletion
    • \n
  • Code analysis and refactoring
    • \n
  • Search in files with regular expressions
    • \n
  • Intelligent selections, including:
      \n
    • Selecting to word right or left
      • \n
    • Selecting to line end or start
      • \n
    • Selecting to document end or start
      • \n
    \n
    • \n
  • Vim and Emacs keybindings
    • \n
  • Line wrapping, to a defined column or the width of the browser window
    • \n
  • Support for a command line
    • \n
  • Support for spaces and real tabs
    • \n
\n\n
" + "filename": "project_bar", + "mtime": 1416491265000, + "pageTitle": "The Project Bar", + "contents": "\n

The Project Bar

\n

Note:

this article is outdated, a new version will follow soon\n\n
\n

The project bar is located towards the left of the Cloud9 IDE: \"The

\n

The buttons in the project bar allow you to reveal and hide panels for the IDE. In more detail:

\n
    \n
  • Pressing on the Cloud9 icon collapses the panel area
    • \n
  • Project Files shows your workspace's directory structure. You can view all your files here. Right-clicking within this panel reveals a drop-down menu with additional options, such as the ability to rename files or create new directories.
    • \n
  • Active Files lists your files that are currently open.
    • \n
  • Run & Debug lets you run and debug your code live, in the browser. For more information, see the section on "Running and Debugging Your Code".
    • \n
  • Deploy allows you to deploy to a variety of services. For more information, see the section on "Deploying Your Code".
    • \n
  • Preferences lets you change the behavior of the editor. The Preferences documentation is provided on its own page.
    • \n
\n

Clicking on any button expands its menu. Clicking on an expanded menu causes it to collapse, which gives you more room in the IDE to work with.

\n\n
" }, { - "filename": "ide_preferences", - "mtime": 1412172002000, - "pageTitle": "IDE Preferences", - "contents": "

IDE Preferences

\n

Note:

this article is outdated, a new version will follow soon\n\n
\n

There are many different ways to configure the IDE. Below is a list of the options available, and what they do.

\n

Note:

All of these options are on a per-project basis. Changing them in one project does not affect any another.\n\n
\n

General

\n

This section controls the overall IDE behavior:

\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
Preference NameDescription
Enable UI AnimationsEnables or disables fluid animations for various UI elements, such as the Project Bar
Animate ScrollingEnables or disables fluid animations when scrolling through code (such as for goto line)
Enable Auto-SaveIf enabled, automatically saves your files on every change
On Save, Strip WhitespaceWhen saving a file, you can remove all extraneous whitespace from your code lines
Reveal Active File in Project TreeEnabling this jumps the project tree to the active file whenever a tab changes to a different file
Warn Before ExitingPrevents accidental data loss by showing a dialog asking if you really want to leave Cloud9 IDE when closing your browser
Node.js RuntimeDefines the default runtime for your Node.js code. "Auto" is based on whatever is in the package.json file, while "Default" reverts to Node 0.6.x.
KeybindingsAllows you to choose which operating system to use for keyboard shortcuts
\n

Language Support

\n

This section controls language analysis options:

\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
\n \n \n \n \n \n \n \n
Preference NameDescription
Enable Hints and Warnings RulesPresents information about your code in the gutter
Highlight Variable InstancesHighlights variable instances in your code
Mark Undeclared VariablesProvides warnings if a variable is being used and has not been declared yet
Mark Unused Function ArgumentsProvides a strikethrough for arguments in a function that are not being used
Warning LevelSpecifies the minimum level of information severity you want provided in the gutter
\n

Code Editor

\n

This section controls language analysis options:

\n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
Preference NameDescription
Auto-pair Quotes, Brackets, etc.When enabled, typing ", (, or [ will actually make two characters appear. In addition, whenever you highlight a word and type one of these characters, it is surrounded by that character (e.g. words becomes "words")
Full Line SelectionWhen highlighting lines, this option will highlight all ending whitespace, until the end of the editor window
Highlight Active LinePresents a darker shade in the code editor to indicate which line you're currently on
Highlight Gutter LinePresents a darker shade in the gutter which line you're currently on
Show Invisible CharactersShows invisibles characters in the editor, like tabs and line breaks
Show Indent GuidesShows the indent guides in the editor, letting you see your code's nestings
Show GutterShows the gutter in the editor, which indicates line numbers, warnings, and errors
Highlight Selected WordIf you highlight a word, this highlights all matching words in the editor
Auto-hide Horizontal ScrollWhen this is enabled, this will hide the horizontal scroll bar in the editor. Note that this has no effect in Mac OS X 10.7 (Lion) and above, since all scrollbars, by default, auto-hide.
Vim ModeWhen enabled, allows you to use vim keybindings in the IDE
Code FoldingWhen enabled, allows you to show or hide "blocks" of code
Fade Fold WidgetsWhen enabled, fades the folding widgets in the gutter
Font SizeChanges the font size of the code in the editor
Show Print MarginShows (and defines) the number of characters possible in line, before it wraps
Soft TabsIndicates how many spaces a single tab represents
Mouse Scroll SpeedDefines the speed of the mouse scrolls
Newline ModeSpecifies the newline mode for the IDE
\n

Terminal

\n

This section controls the behavior for the terminal:

\n
\n \n \n \n \n \n \n \n
\n \n \n \n \n \n \n \n \n \n \n
\n \n \n \n
Preference NameDescription
ScrollbackSets the scrollback buffer for the terminal
Font FamilySets the font for the terminal
Font SizeSets the font size for the terminal
Blinking CursorSpecifies whether or not you want the cursor to blink
\n

Code Tools

\n

This section controls the various tools that are available in the IDE:

\n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n
Preference NameDescription
Enable Color PickerMakes the color picker available for use
Preserve Empty LinesWhen enabled, the editor keeps any new lines without text
Keep Array IndentionWhen enabled, tabs and newlines in arrays are preserved. For example, the follow array would remain as-is with this option:\n 
\n        var o = [{\n            a: b\n        }, {\n            c: d\n        }];\n
\n
JSLint Strict WhitespaceIf selected, all brackets are preceded by a space. For example, if(x){ becomes if (x) {, and function(arg){ becomes function (arg) {
BracesThese options control how braces are handled in the IDE:\n
    \n
  • Braces with control statement: braces are left "in-line" alongside the code statements. For example, code is formatted like this:\n 
    \n    if (true) {\n        var x = 3;\n    } else {\n        var x = 5;\n    }\n
    \n
    • \n
  • Braces on own line: braces are always placed on their own line. For example, code is formatted like this:\n 
    \n    if (true)\n    {\n        var x = 3;\n    } else\n    {\n        var x = 5;\n    }\n
    \n
    • \n
  • End braces on own line: only the ending braces have their own line. For example, code is formatted like this:\n 
    \n    if (true) {\n        var x = 3;\n    }\n    else {\n        var x = 5;\n    }\n
    \n
    • \n
\n
\n
" + "filename": "status_bar", + "mtime": 1416491265000, + "pageTitle": "Status Bar", + "contents": "\n

Status Bar

\n

Note:

this feature is deprecated\n\n
\n

The status bar is designed to provide you with all sorts of information about your code--and additional functionality--without getting in the way of the IDE. It's quite tiny, and quite powerful, like a weight-lifting squirrel.

\n

You can find the status bar in the lower-right corner of the editor: \"The. Keep in mind that the status bar is transparent, so it's able to camoflauge well with light or dark themes.

\n

There's three pieces of crucial information available at all times: your current row, your current column, and, if you're highlighting characters, the status bar displays the number of bytes currently selected. If you're using Vim Mode, the status bar also tells you if you're in INSERT mode.

\n

If you click on the status bar, it expands into a menu that provides a smaller set of the full IDE preferences. These options only deal with the IDE editor:

\n
\n \n \n \n \n \n \n \n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
Preference NameDescription
Show InvisiblesShows invisibles characters in the editor, like tabs and line breaks
Wraps LinesWraps lines according to the line margin defined, or your browser's window. Otherwise, lines run off the current viewport.
Code FoldingWhen enabled, allows you to show or hide "blocks" of code
Full Line SelectionWhen highlighting lines, this option will highlight all ending whitespace, until the end of the editor window
Highlight Active LinePresents a darker shade in the code editor to indicate which line you're currently on
Show Indent GuidesShows the indent guides in the editor, letting you see your code's nestings
Show GutterShows the gutter in the editor, which indicates line numbers, warnings, and errors
Highlight Selected WordIf you highlight a word, this highlights all matching words in the editor
Auto-pair Quotes, Brackets, etc.When enabled, typing ", (, or [ will actually make two characters appear. In addition, whenever you highlight a word and type one of these characters, it is surrounded by that character (e.g. words becomes "words")
Auto-hide Horizontal Scrollbarhen this is enabled, this will hide the horizontal scroll bar in the editor. Note that this has no effect in Mac OS X 10.7 (Lion) and above, since all scrollbars, by default, auto-hide.
Font SizeChanges the font size of the code in the editor
Show Print MarginShows (and defines) the number of characters possible in line, before it wraps
Soft TabsIndicates how many spaces a single tab represents
Mouse Scroll SpeedDefines the speed of the mouse scrolls
\n
\n
" }, { "filename": "terminal", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Terminal", "contents": "\n

Terminal

\n

Note:

this article is outdated, a new version will follow soon\n\n
\n

The terminal provides you with a TTY interface for direct access to the machine that Cloud9 is running on. If you're running your own workspace, this is the server you've SSH'ed into. If you're using the hosted Cloud9 platform, this is the server your code runs on.

\n

Warning:

While certain operations, like sudo, are restricted, you can completely destroy your workspace, by doing something like rm -rf. Use your power wisely!\n\n
\n

To create a new terminal, go to View > Terminals > New Terminal, or simply type Alt-T on the keyboard. The terminal has the following capabilities:

\n
    \n
  • Perform all Unix commands
    • \n
  • You can create more than one instance of a terminal (by just creating a new tab)
    • \n
  • The terminal allows for path autocompletion by hitting Tab
    • \n
\n

\"Screenshot

\n\n
" }, { - "filename": "frameworks_jekyll", - "mtime": 1416998221000, - "pageTitle": "Framework: Jekyll", - "contents": "\n

Framework: Jekyll

\n

Jekyll is a great static site generator, also used by github pages. You simply need to install the Ruby gem and then make sure you pass the right port to the serve command.

\n
$ gem install jekyll\n$ jekyll new my-awesome-site\n$ cd my-awesome-site\n$ jekyll serve --port $PORT
\n\n
" + "filename": "tab_functions", + "mtime": 1416491265000, + "pageTitle": "Tab Functions", + "contents": "

Tab Functions

\n

Note:

this article is outdated, a new version will follow soon\n\n
\n

Cloud9 IDE offers advanced tab features to make working with multiple files easy. By right-clicking on any tab, you'll open up the tab context menu:

\n

\"The

\n

These feature include:

\n
    \n
  • Reveal in File Tree: opens the current file in the Project Files tree
    • \n
  • Close Tab: closes the current tab
    • \n
  • Close All Tabs: closes all the opened files
    • \n
  • Close All But Current Tab: closes all the opened files, except the current one
    • \n
  • Close Tabs to the Right/Left: closes all opened tabs to the right (or left) of the current one
    • \n
  • File Revision History...: launches the revisions panel
    • \n
\n

To the left of the tab menu is another button that offers additional functions for tab navigation:
\"The

\n

Tab Sessions

\n
\n\n
\n\n

Tab sessions is a unique feature that is useful when dealing with projects that involve juggling between many tabs. Essentially, tab sessions lets you save the current state of the tabs. You can close your workspace, switch to a different branch, and instantly reload your previously opened files. You'll no longer need to work with opening and closing multiple files.

\n

To use tab sessions, select Save Tab Sessions from the tab button menu. Give it a unique name. When you're ready to restore your tab sessions, just select Load Tab Sessions.

\n

If you find that you've got too many tab sessions defined, you can always choose to delete them from the same tab menu.

\n\n
" + }, + { + "filename": "the_editor", + "mtime": 1416491265000, + "pageTitle": "The Editor", + "contents": "\n

The Editor

\n

The editor is the most important element of any IDE; that's why Cloud9 developed ACE. ACE is a high-performance code editor for the web that supports over 40 different languages, over two dozen themes, and can still work faithfully on large documents (at last count, four million lines of code was the upper limit). It also contains a bevy of features you'd expect from traditional desktop editors. Among these include:

\n
    \n
  • Undo and Redo support
    • \n
  • Cut, Copy, and Paste functionality
    • \n
  • Line manipulation, including:
      \n
    • Indenting and outdenting
      • \n
    • Moving and copying lines up or down
      • \n
    • Removing lines from any point
      • \n
    • Splitting lines
      • \n
    \n
    • \n
  • Highlighting and commenting blocks of code
    • \n
  • Removing words to the right or the left
    • \n
  • Transposing letters
    • \n
  • Code folding (including the entire file)
    • \n
  • Converting cases
    • \n
  • Multiple cursors
    • \n
  • Autocompletion
    • \n
  • Code analysis and refactoring
    • \n
  • Search in files with regular expressions
    • \n
  • Intelligent selections, including:
      \n
    • Selecting to word right or left
      • \n
    • Selecting to line end or start
      • \n
    • Selecting to document end or start
      • \n
    \n
    • \n
  • Vim and Emacs keybindings
    • \n
  • Line wrapping, to a defined column or the width of the browser window
    • \n
  • Support for a command line
    • \n
  • Support for spaces and real tabs
    • \n
\n\n
" }, { "filename": "index", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Cloud9 IDE User Documentation", - "contents": "{\n \"files\": [\n {\n \"filename\": \"deploying_code\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Deploying Your Code\",\n \"contents\": \"\\n

Deploying Your Code

\\n

Cloud9 IDE offers many different ways to get your code from your editor to your \\nproduction server. To deploy your code, click on the Deploy button in the \\nProject Bar:

\\n

\\\"The

\\n

We offer tight integration with the following environments:

\\n\\n

Following these links will provide you with more information on code deployment.\\nYou can deploy your code to as many services and servers as you like. Keep in \\nmind that you'll already need an account at those hosting providers before you \\ncan deploy your app to them!

\\n

If you're comfortable with the command line, you can also deploy to several more\\nenvironments, such as:

\\n\\n

Warning:

Before you attempt to deploy your application, make sure that you have \\ncommitted all your changes to version control. Cloud9 deploys for you whatever \\nwas last committed to version control.
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"deploying_to_heroku\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Deploying to Heroku\",\n \"contents\": \"\\n

Deploying to Heroku

\\n

This section will show you how to deploy your applications to Heroku, a cloud-based application platform. The integration with Cloud9 IDE makes your development process even more agile. If you don't have a Heroku account, visit their website to create one for free.

\\n

To get started, create a simple Node.js application. If you don't have one yet, you can follow our tutorial on developing one.

\\n

After you click on the Deploy button in the Project Bar, click the plus sign next to Deploy to add another deploy target. Choose Heroku as an option. After you have signed into your Heroku account, you can create a new deploy target or choose an existing one from your account:

\\n

\\\"Showing

\\n

Note:

Heroku only allows you to create names for your apps that contain letters and dashes.\\n\\n
\\n

Next, press Deploy to continue the process; the following window might appear:

\\n

\\\"Dialog

\\n

Heroku Node.js apps are required to have a package.json file, much like with NPM. Cloud9 can generate a package.json file for you, containing metadata to share Heroku. The following lines represent what that file might looks like:

\\n
{\\n    \\\"name\\\": \\\"cloud9-heroku-example\\\",\\n    \\\"version\\\": \\\"0.0.1\\\"\\n}
\\n

After you have a package.json file, you might see this dialog:

\\n

\\\"Dialog

\\n

Sometimes, a Heroku app also requires a Procfile. The Procfile is needed to start the application in Heroku. You can just create a new file, add the line below, and save it as 'Procfile'. Don't add any file extensions.

\\n
web: node web.js
\\n

Try the deploy button again. The console will directly output the following when the deployment is completed:

\\n

\\\"Console

\\n

And just like that, you've deployed your project to Heroku.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"deploying_to_windows_azure_sites\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Deploying to Windows Azure Sites\",\n \"contents\": \"\\n

Deploying to Windows Azure Sites

\\n

This article will show you how to deploy your applications to Windows Azure. If you don't have an account yet, the Windows Azure process will help you create one. Keep in mind that Windows Azure is not free, though it does come with a free trial. Windows Azure projects can be deployed from any operating system.

\\n

To get started, create a simple Node.js application. If you don't have one yet, you can follow our tutorial on developing one.

\\n

After you click on the Deploy button in the Project Bar, click the plus sign next to Deploy to add another deploy target. Choose Windows Azure as an option. You'll be prompted with this dialog:
\\\"Windows

\\n

You must click on the Download Windows Azure Settings button before you can continue. If you don't have a Windows Azure account, here is where you can create one. If you do have an account, your browser will automatically download the required file.

\\n

When that's finished, simply select the downloaded file from your computer, and upload it to Cloud9. You'll only have to do this process once. If you ever need to upload a new certificate, be sure to click Clear cert in the lower-right corner of this dialog.

\\n

After the file has uploaded, click on Create new to create a new hosted service. A hosted service is the container in which your application is hosted when it is deployed to Windows Azure. For more information, see Overview of Creating a Hosted Service for Windows Azure.

\\n

You can set a few configuration options such as the number of instances to use, its host OS, and where the data center is located. Selecting "Enable RDP" and providing a username and password enables remote desktop for your deployment.

\\n

Your new Windows Azure server will appear in the Deploy list:
\\\"Windows

\\n

Go ahead and click on DEPLOY. If this is the first time you're trying to deploy this project to Windows Azure, you'll receive three prompts:

\\n
    \\n

  1. A dialog will inform you of a missing web.config file. If you click Yes, Cloud9 will create a file called Web.cloud.config in your project. This file contains configuration information about your app.

    \\n
    2. \\n

  2. You'll be told about a missing csdef file. If you click Yes, Cloud9 will create a file called ServiceDefinition.csdef in your project. ServiceDefinition.csdef is a Windows Azure-specific files necessary for publishing your application For more information, see Overview of Creating a Hosted Service for Windows Azure.

    \\n
    3. \\n

  3. You'll be asked to select the instance size for this application. For this tutorial, just select Small, and then click Create. For more details about Windows Azure VM sizes, see How to Configure Virtual Machine Sizes.

    \\n
    4. \\n
\\n

Your app will now deploy to a Windows Azure server! You can follow its progress in the Deploy panel, or by watching the messages in the console:\\n\\\"Windows

\\n

For more information on configuring your app on the Windows Azure website, see Deploying a Windows Azure App from Cloud9.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"deploying_via_cli\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Deploying via the Command Line\",\n \"contents\": \"\\n
\\n

Deploying via the Command Line

\\n

In the new version of Cloud9 we don't have support for deployment from the UI yet, but we're going to add those features soon.

\\n

Until then, you can manually install various command-line tools into your workspace and deploy using the command line. \\nIt should go without saying that this is for super 31337 developers that aren't afraid of the command line.

\\n

Below is a list of some of the services we have tested and support deploying to. \\nAll the commands need to be executed in the terminal unless stated otherwise.

\\n

Heroku

\\n

Heroku's toolbelt is installed by default in new VMs.

\\n

Now, you can use the heroku command for your projects, as described in the \\nHeroku documentation.

\\n

If deploying to Heroku, you should probably be using a local instance of PostgresQL, or you may run into problems caused by different database interpretations of SQL.

\\n

Windows Azure Web Sites

\\n

Free and Premium Plans

\\n

In the Console or a Terminal, type the \\nfollowing:

\\n
npm install azure
\\n

Now, you can use the azure command from the Console/Terminal. For more \\ninformation, read the official azure documentation.

\\n

Premium Plans

\\n

To deploy to Azure sites from the command line, open the Terminal and type:

\\n
cd ~/lib/azure-sites\\nnpm install
\\n

Then, add the bin to your workspace's path:

\\n
PATH=$PATH:$HOME/lib/azure-sites/bin
\\n

Now, you can use the azure command in the terminal.

\\n

Windows Azure Cloud Services

\\n

For free and premium plans, follow the instructions on the \\nazure-cmdlet-node repository. This \\nproject is maintained by Cloud9.

\\n

Google App Engine

\\n

First, setup Push to Deploy: Create a new App Engine application at \\ncloud.google.com/console, and then enable \\nPush-to-Deploy under 'App Engine' in the Application Settings page. Leave this \\ntab open to note the URL for your repo.

\\n

Secondly, configure Cloud9. Run the following commands (making sure to replace \\nyour email address, auth-token, and repo-url):

\\n
echo \\\"machine code.google.com login EMAIL password PASSWORD\\\" >> ~/.netrc\\ngit remote add appengine REPO
\\n

Note:

The email in this case is the mail address you use to login to your Google\\nApp Engine account and the password is the auth-token generated from the admin\\nconsole, it is not your google password, never type that into a third party tool.\\n'REPO' is the repository URL generated before.\\n\\n
\\n

Finally, do a commit, and a push:

\\n
git commit -a -m \\\"First commit\\\"\\ngit push appengine master
\\n

OpenShift

\\n
# Install rhc:\\ngem install rhc\\nrhc setup\\n\\n# After this you can use rhc to manage your account:\\n\\n# list apps:\\nrhc apps\\n# To show what you can do with apps do:\\nrhc app help\\n# You deploy via a git push\\ngit push <giturl> master
\\n

CloudFoundry

\\n

To deploy to CloudFoundry from the command line in the Console \\nor a Terminal, type:

\\n
cd ~\\nwget https://github.com/cloudfoundry/vmc/zipball/master\\nmv master cloudfoundry\\nunzip cloudfoundry\\ncd cloudfoundry-vmc-nnnn\\nbundle
\\n

NodeJitsu

\\n

Free and Premium Plans

\\n

In the the Console or a Terminal, type:

\\n
npm install jitsu@0.7.x -g\\nmkdir node_modules\\nmv ../lib/node_modules/jitsu node_modules
\\n

Now, you can run jitsu from the command line. For more information, see \\nthe official jitsu documentation.

\\n

Premium Plans

\\n
npm install jitsu@0.7.x -g
\\n

You can now run jitsu from both the Console and the Terminal.

\\n

Modulus

\\n

In the the Console or a Terminal, type:

\\n
npm install modulus -g
\\n

Now, you can run modulus from the command line. For more information, see \\nthe official modulus documentation.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"faq_general\",\n \"mtime\": 1416998245000,\n \"pageTitle\": \"FAQ: General\",\n \"contents\": \"\\n
\\n

FAQ: General

\\n

Can I use FTP workspaces on Cloud9?

\\n

Yes, Cloud9 supports FTP workspaces that allow you to edit your files directly on your FTP server. \\nCurrently FTP workspaces still open in the old version of Cloud9, but soon we'll also support FTP workspaces with the new version of Cloud9.

\\n

One thing that was removed for reliability reasons in the new version of Cloud9, is the ability to deploy over FTP from a regular workspace.\\nWe're bringing back those features in a new format and with much higher reliability in the coming months.

\\n

How do I deploy to Heroku/Openshift/Azure/...?

\\n

See Deploying via CLI.

\\n

Can I connect to SMTP servers (port 25)?

\\n

No, this is not supported by our hosting platform. It does currently allow access to the GMail servers though, so you can use that service during development.

\\n

My workspace says it's out of quota. how do I fix it?

\\n

You can inspect your current quota usage with the df command in the Terminal:

\\n
$ df
\\n

To find which files and directories are consuming a lot of space, go to a directory such as your home directory, and run this command:

\\n
$ du -m -d 1 -a | sort -n
\\n

This should give you a list of all members of that directory and how much space they use in megabytes.

\\n

Alternatively, try du-c9 for seeing all files you added to your workspace and account for the quota.

\\n

Can I use two-factor authentication with Cloud9?

\\n

You can sign into Cloud9 with your github or bitbucket account and set that up to use two-factor authentication.\\nWe don't currently provide an option to directly setup your Cloud9 account for two-factor authentication.

\\n

I can't preview my running app.

\\n

Try using port 8080 instead, which often solves this case.

\\n

EADDRINUSE: My app complains that the address/port is in use

\\n

Applications won't start if another application is already listening to the same port. In order to fix it you first need to find out which process that is:

\\n
$ netstat -nlp | grep $PORT
\\n

This will report the process id (PID) which you can then kill using

\\n
$ sudo kill -9 <PID>
\\n

Often apache is still running in the background. In that case you can kill it using

\\n
$ sudo pkill apache2
\\n

How can I upload local files to my project?

\\n

Either drag a local file directly from your desktop into the Cloud9 file tree,\\nor use the "File > Upload Local Files" menu item.

\\n

How can I download my project files?

\\n

Use "File > Download project". Currently, this will give you a .tar.gz file, which\\nensures maximum portability. To open these files, you can use something like\\nWinRAR or 7-zip.

\\n

How can I share a single directory of a private workspace

\\n

Sometime you might want others to open a file or directory in the browser \\nwithout opening up the whole workspace. This can be done by starting a small \\nhttp server in that directory and make sure that the running application is public.

\\n

To make the running application public you have to click the "sharing" button at\\nthe top right and the check "public" for application.

\\n

To run the server open a terminal and do

\\n
$ cd /dir/i/want/to/share\\n$ python3 -m http.server 8080
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"faq_ssh\",\n \"mtime\": 1416998221000,\n \"pageTitle\": \"FAQ: SSH workspaces\",\n \"contents\": \"\\n
\\n

FAQ: SSH workspaces

\\n

I cannot create a SSH workspace using a Digital Ocean droplet

\\n

We recently discovered our web host is blocking connections to some Digital Ocean IP addresses because they suspect they are being used by Iranian users. They are legally forced to block them.

\\n

Digital Ocean maintains a whitelist of droplet IP addresses which should not be blocked and our web host follows this list.

\\n

Please raise a support ticket with Digital Ocean mentioning that you would like to have your droplet IP added to the whitelist. After this is complete you will be able to create your SSH workspace within 24 - 48 hours.

\\n

I'm getting an error on the SSH install script: "ncurses not found"

\\n

Try executing the following command:

\\n
yum install ncurses-devel
\\n

or

\\n
yum install glibc-static
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"faq_php\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"FAQ: PHP\",\n \"contents\": \"\\n
\\n

FAQ: PHP

\\n

where are the Apache logs?

\\n

By default the logs are in ~/lib/apache2/log

\\n

Is mail() supported?

\\n

No, this is currently not supported; see FAQ: General about SMTP access.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"faq_python\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"FAQ: Python\",\n \"contents\": \"\\n
\\n

FAQ: Python

\\n

Why does easy_install report a permission_denied error?

\\n

Please use sudo easy_install instead.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"colorpicker\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Color Picker\",\n \"contents\": \"\\n

Color Picker

\\n

Note:

this feature is deprecated\\n\\n
\\n
\\n\\n
\\n\\n

The color picker is an awesome feature in Cloud9 IDE, designed to not only make color selections easier, but also, more harmonious. At its core, the color picker is a way to represent words (red, blue, e.t.c.), RGBA values (rgba(175, 3, 124, .6)), or hex values (#f00f00) into actual colors.

\\n

To enable the color picker, flip the preferences on in the Settings panel. You can use the color picker in CSS, SVG, HTML, or APF Skin files. All you have to do is hover over the value of a color definition, and it'll instantly highlight, like this: \\\"Color

\\n

When the represented color is highlighted, click on it. You'll get a color square defining all the possible color arrangements. To select a color, you can click in the square, pick your own RGB or HSB values, or enter some hex code. Best of all, at the bottom of the window, you'll find a list of other colors found within the same document--just in case you want to achieve matching shades:
\\\"Color

\\n

To set the value, just click anywhere outside of the color picker.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"language_analysis\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Language Analysis\",\n \"contents\": \"\\n
\\n

Language Analysis

\\n

For JavaScript files, Cloud9 provides analysis using a combination of our own analysis tools, as well as JSHint (specifically for Javascript code). Our language analysis can't detect if your program is correct, fast, or has memory leaks, but it can save you time by spotting things like undeclared variables, syntax errors, or other preventable typos.

\\n

When Cloud9 detects an issue with your code, an icon appears in the gutter for the offending lines of code. There are three types of identifiers available for your code:

\\n
    \\n
  • Informational (\\\"Little): these are non-critical, non-dangerous updates about your code
    • \\n
  • Warnings (\\\"Warning): these are potentially incorrect pieces of code
    • \\n
  • Errors (\\\"Error): these are incorrect lines of code that will almost certainly throw a runtime error when you try to run your script
    • \\n
\\n

If you hover over any of these icons in the gutter, you'll get a pop-up that presents some information as to what, exactly, the problem is. For example, suppose we have a variable declared, called fs, that is never used:
\\\"fs

\\n

Notice also that fs has a strikethrough, to provide further visual clues that something is not quite right.

\\n

If you're concerned with the level of information that's listed in the gutter, you can always configure its "strictness" in the IDE preferences. For example, you could choose to hide every icon that isn't a warning or an error.

\\n

Configuring Global Options

\\n

JSHint provides additional configuration options that Cloud9 incorporates on a per-file basis. Typically, you declare these options as comments at the very top of a file, like this:

\\n
/*jshint curly:true, debug:true */
\\n

For a full list of the JSHint configutation options, please check the documentation page describing them.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"autocompletion\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Code Autocompletion\",\n \"contents\": \"\\n

Code Autocompletion

\\n

For Javascript programs, Cloud9 IDE provides intelligent and responsive autocompletion for your code. Autocompletion is based not only on the content within your files, but also on the ECMAScript and Node.js standard library:

\\n

\\\"Autocompletion

\\n

Methods defined in ECMAScript and Node.js also have documentation provided for you. Simply hover over a method name for a moment, and a second box quickly shows some additional information.

\\n

You can disable autocompletion in the Settings menu.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"custom_runners\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Custom Runners\",\n \"contents\": \"\\n
\\n

Custom Runners

\\n

Luckily you're not limited to the default set of Runners in Cloud9.\\nYou can simply define your own custom Runner, which is both simple and very powerful.\\nAll you need to do is create a Runner file.\\nIn this article we'll describe how to do this in just a few steps.

\\n

In the Run panel (usually at the bottom of the UI), click the 'Runner' text input and choose 'New Runner'. \\nIn the new Runner file that's now opened, you can configure your runner\\nusing a simple JSON format. We'll show a basic example below\\nand then explain the different properties you can use.

\\n

Let's start with a basic example: a runner for go files.

\\n
{\\n    \\\"cmd\\\": [\\\"go\\\", \\\"run\\\", \\\"$file\\\", \\\"$args\\\"],\\n    \\\"selector\\\": \\\"source.go\\\",\\n    \\\"info\\\": \\\"Your code is running :)\\\"\\n}
\\n

This runner will use "go run" for any file that has a ".go" file extension.\\nIf you add it, it'll override our default Go runner.

\\n

As another example, let's save a new Node 0.11 configuration, including Harmony support. \\nCreate a new Runner, add this code, and save it as 'Node 0.11.x.run':

\\n
// This file overrides the built-in Node 0.11.x runner\\n// For more information see http://docs.c9.io:8080/#!/api/run-method-run\\n{\\n  \\\"cmd\\\": [\\n    \\\"bash\\\",\\n    \\\"--login\\\",\\n    \\\"-c\\\",\\n    \\\"nvm use 0.11 > /dev/null; node --harmony ${debug?--nocrankshaft --nolazy --debug-brk=15454} '$file' $args\\\"\\n  ],\\n  \\\"debugger\\\": \\\"v8\\\",\\n  \\\"debugport\\\": 15454,\\n  \\\"info\\\": \\\"Your code is running at \\\\\\\\033[01;34m$url\\\\\\\\033[00m.\\\\n\\\\\\\\033[01;31mImportant:\\\\\\\\033[00m use \\\\\\\\033[01;32mprocess.env.PORT\\\\\\\\033[00m as the port and \\\\\\\\033[01;32mprocess.env.IP\\\\\\\\033[00m as the host in your scripts!\\\\n\\\"\\n}
\\n

Note:

alternatively, you can check 'Show Hidden Files' in your workspace directory tree (the small gear in the upper right corner), and create a new file in the '.c9/runners' folder called 'Node 0.11.x.run' with this code.\\n\\n
\\n

That's it! Your custom Runner should be available in the Run panel.

\\n

Runner Variables

\\n

Here's a list of all the variables you can use in your runners:

\\n
    \\n

  • $file_path The directory of the current file, e. g., /home/ubuntu/workspace/docs

    \\n
    • \\n

  • $file The full path to the current file, e. g., /home/ubuntu/workspace/docs/Chapter1.txt.

    \\n
    • \\n

  • $args Any arguments entered after the file name.

    \\n
    • \\n

  • $file_name The name portion of the current file, e. g., Chapter1.txt.

    \\n
    • \\n

  • $file_extension The extension portion of the current file, e. g., txt.

    \\n
    • \\n

  • $file_base_name The name only portion of the current file, e. g., Document.

    \\n
    • \\n

  • $packages The full path to the Packages folder.

    \\n
    • \\n

  • $project The full path to the current project file.

    \\n
    • \\n

  • $project_path The directory of the current project file.

    \\n
    • \\n

  • $project_name The name portion of the current project file.

    \\n
    • \\n

  • $project_extension The extension portion of the current project file.

    \\n
    • \\n

  • $project_base_name The name only portion of the current project file.

    \\n
    • \\n

  • $hostname The hostname of the workspace.

    \\n
    • \\n

  • $hostname_path The hostname of the workspace together with the relative path of the project file.

    \\n
    • \\n

  • $url The full url to access the workspace.

    \\n
    • \\n

  • $port The port assigned to the workspace.

    \\n
    • \\n

  • $ip The ip address to run a process against in the workspace.

    \\n
    • \\n
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"gotofile_and_definition\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Using Goto File and Goto Definition\",\n \"contents\": \"\\n

Using Goto File and Goto Definition

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n
\\n\\n
\\n\\n

Let's say you're working a large project containing many files, and you kind-of sort-of know the name of a file that you want to open up. Goto File is our feature to help you quickly and easily jump to any file in your workspace, without the need to search through different directories. Simply hit Cmd-E (or Ctrl-E on Unix/Windows) and away you go:

\\n

\\\"Goto

\\n

Goto File offers filtering for any portion of a filename, including directories. Search for the beginning, middle, or end of a file path, or even just an extension, like .js, and Goto File with instantly present the results to you. Clicking on a name in the list opens the file right up. Goto File does not support case-insensitive, wildcard (*, ?), or regular expression (., +) searching.

\\n

Goto Definition takes the same concept and applies it to files. You can easily navigate between classes and members defined in your files. By entering text, you can filter your class' member results. Finally, as you navigate through your file, Cloud9 IDE will jump to the relevant portion of the code:

\\n

\\\"Goto

\\n

Note:

Currently, Goto Definition only works for Javascript files.\\n\\n
\\n

Another feature that's available is the capability to "jump to definition." If your cursor is on a variable or function name, you can tap F12 (or type jumptodef in the console) to instantly scroll the editor to the member's definition.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"collaboration\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Collaboration\",\n \"contents\": \"\\n
\\n

Collaboration

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n

Collaboration with Cloud9 IDE is an amazing feature that lets you do more than just share your projects with any other Cloud9 developer. You can grant someone else access to change files in your workspace, in realtime--or just let them view the workspace without any other rights. While you're collaborating, you can discuss the code through a built-in chat room.

\\n

To invite someone to collaborate on a project with you, simply copy the URL in the browser and send it to a friend. You can also click on Share in the menu bar to get quick access to other ways to share, such as via e-mail, Twitter, or Facebook.

\\n

Let's take a look at some of the additional features available while you collaborate.

\\n

Members List

\\n

There are two terms used for people accessing your project: members and visitors. Members are individuals that have read and write access to your project--that means they can change any code; visitors only have read access. The Members panel lists all the collaborators in a project, both active and inactive:

\\n

\\\"The

\\n

If you are the owner of a project, you can click on anyone's username to grant (or revoke) write access:

\\n

\\\"Granting

\\n

If you're worried about the sanctity of your code after grant access to other developers, fear not. You can always take a look at a file revision history to view line-by-line changes made to your project over time.

\\n

Chatting

\\n

Any member or visitor can participate in group chat with each other. Developers can also choose to double-click on a person's username and engage in a private, instant-message-style conversation.

\\n

Collaborate on Code

\\n

When a collaborator changes a file you're also working on, Cloud9 detects it and asks you whether you'd like to use their changes, or your version. We're also simply giving you the option to merge both, using a three-way-merge algorithm to handle any conflicts. This is the same algorithm used by version control systems like git for merging branches.

\\n

To make the experience even smoother you can choose "Always merge by default" and we'll never interrupt you about file changes again.

\\n

Check out the video below to see this in action.

\\n
\\n\\n
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"searching_in_files\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Searching and Replacing in Files\",\n \"contents\": \"\\n
\\n

Searching and Replacing in Files

\\n
\\n\\n
\\n\\n

Aside from Goto File and Goto Definition, Cloud9 also offers more traditional search functionality. There are three types of search modes available: quicksearch, search and replace, and find in files.

\\n

Quicksearch

\\n

Quicksearch can be activated by hitting Cmd-F on a Mac, or Ctrl-F on a Unix/Windows machine. As you type in the quicksearch bar, the IDE instantly shifts to the next available result. This is a great way to quickly search around in your code without hassle.

\\n

Quicksearch offers the following options:

\\n
    \\n
  • Regular Expressions: when enabled, your search is treated as a regular expression
    • \\n
  • Match Case: when enabled, your search takes capitalizations seriously:
    • \\n
  • Whole Words: when enabled, your search will only be considered for whole words:
    • \\n
  • Search Backwards: when enabled, the search goes backwards, instead of forwards
    • \\n
  • Wrap Around: when enabled, the search loops around the file, from bottom to top
    • \\n
  • Search Selection: when enabled, the search only considers code that you've currently highlighted
    • \\n
\\n

Search and Replace

\\n

Building on the features of quicksearch, search and replace allows you to replace segments of code in your file. You can again continue to use regular expressions, keeping in mind the groupings are prefixed with a dollar sign, i.e. $1.

\\n

Replacing offers two more options:

\\n
    \\n
  • Preserve Case: if enabled, case is preserved while replacing content
    • \\n
  • Highlight Matches: if enabled, the new replaced matches are highlighted in the document
    • \\n
\\n

Find in Files

\\n

In order to search across a set of files, you'll want to use the Find in Files feature. Here, you can search of a string or regular expression, within your entire workspace or a single directory. You can also filter based on extensions, like *.js or *.rb.

\\n

Find in files offers some of the same search options as quicksearch:

\\n
    \\n
  • Regular Expressions: when enabled, your search is treated as a regular expression
    • \\n
  • Match Case: when enabled, your search takes capitalizations seriously
    • \\n
  • Whole Words: when enabled, your search will only be considered for whole words
    • \\n
\\n

One more feature of find in files is the ability to render search results either in the console or the IDE. You can fold results to keep them out of the way, or, edited the file if you're working down a list:
\\\"Search

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"multiple_cursors\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Multiple Cursors\",\n \"contents\": \"\\n

Multiple Cursors

\\n

Multiple cursors is one of the most useful features available in the Cloud9 editor. You can use multiple cursors to perform tasks like rename several variables or members at once, break up lists separated by commas, or insert the same text in multiple locations.

\\n

\\\"Showing

\\n

Multiple selections can be copied and pasted, and you can insert or remove entire lines in several locations.

\\n

There are several ways to get access to mutliple cursors:

\\n
    \\n
  • Via keyboard shortcuts, you can create a new cursor in any direction
    • \\n
  • By holding the Alt key, clicking the mouse, and dragging the cursor up or down in the editor
    • \\n
  • Through the menu bar at Selection > Multiple Selections
    • \\n
\\n

One of the best capabilities is the ability to instantly select the next instance of your currently highlighted section. This is especially useful for refactoring several parts of the code at once. To do this, press Ctrl-Alt, followed by the right (or left) arrow key to navigate around in the code.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"supported_languages\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Supported Languages\",\n \"contents\": \"\\n
\\n

Supported Languages

\\n

Cloud9 IDE has varying levels of support for different programming languages. \\nUsually you will at least have Syntax Highlighting in the editor and the ability\\nto run apps from the Terminal.

\\n

Syntax Highlighting

\\n

Cloud9 IDE develops and builds on Ace, an \\neditor for writing code online. Cloud9's Ace editor currently supports \\nhighlighting for about 100 programming languages, and any changes made to Ace are \\nreflected back into Cloud9 IDE.

\\n

The list of supported languages is growing, and you can get the full list from \\nthe View > Syntax menu. Feel free to create an issue in the Ace repository \\nfor new requests, or add your own syntax highlighting mode.

\\n

See Syntax Highlighting & Themes for more \\ninfo.

\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n

Running apps

\\n

The Run panel currently supports running the following by default:

\\n
    \\n
  • Apache httpd (PHP, HTML)
    • \\n
  • Node
    • \\n
  • Python
    • \\n
  • Ruby
    • \\n
  • Ruby on Rails
    • \\n
  • Go
    • \\n
  • CoffeeScript
    • \\n
  • Julia
    • \\n
  • Mocha
    • \\n
  • Shell script
    • \\n
\\n

If you'd like to run any other language, simply create a new "Runner".

\\n

You can also do so from the Terminal. \\nEach workspace is an Ubuntu VM with the standard tools like bash, make, \\ngcc, vim, java SDK or perl pre-installed.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"syntax_highlighting_themes\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Syntax Higlighting and Themes\",\n \"contents\": \"\\n

Syntax Higlighting and Themes

\\n
\\n\\n

Cloud9 IDE develops and builds on Ace, an editor for writing code online. Ace supports over two dozen different themes for highlighting your code, and any changes made to Ace are reflected back into Cloud9 IDE.

\\n

You can change your current theme by going to View > Themes, and selecting from one of the many options. By hovering over the menu items, you'll be able to get a preview of the theme. To activate a theme you like, just click on its name.

\\n

The IDE contains the following themes:

\\n
    \\n
  • Chrome
    • \\n
  • Clouds
    • \\n
  • Clouds Midnight
    • \\n
  • Cobalt
    • \\n
  • Crimson Editor
    • \\n
  • Dawn
    • \\n
  • Eclipse
    • \\n
  • Idle Fingers
    • \\n
  • Kr Theme
    • \\n
  • Merbivore
    • \\n
  • Merbivore Soft
    • \\n
  • Mono Industrial
    • \\n
  • Monokai
    • \\n
  • Pastel On Dark
    • \\n
  • Solarized Dark
    • \\n
  • Solarized Light
    • \\n
  • TextMate
    • \\n
  • Tomorrow
    • \\n
  • Tomorrow Night
    • \\n
  • Tomorrow Night Blue
    • \\n
  • Tomorrow Night Bright
    • \\n
  • Tomorrow Night Eighties
    • \\n
  • Twilight
    • \\n
  • Vibrant Ink
    • \\n
\\n

By default, files are highlighted based on their file extension. You can change this by going to View > Syntax, and selecting a different context. This forces a single file to use a different highlighter.

\\n

We support highlighting for at least the following languages, and many more:

\\n
    \\n
  • CoffeeScript
    • \\n
  • ColdFusion
    • \\n
  • C#
    • \\n
  • CSS
    • \\n
  • Go
    • \\n
  • Groovy
    • \\n
  • haXe
    • \\n
  • HTML
    • \\n
  • C/C++
    • \\n
  • Clojure
    • \\n
  • Java
    • \\n
  • JavaScript
    • \\n
  • JSON
    • \\n
  • LaTeX
    • \\n
  • LESS
    • \\n
  • Liquid
    • \\n
  • Lua
    • \\n
  • Markdown
    • \\n
  • OCaml
    • \\n
  • Perl
    • \\n
  • pgSQL
    • \\n
  • PHP
    • \\n
  • Powershell
    • \\n
  • Python
    • \\n
  • Ruby
    • \\n
  • OpenSCAD
    • \\n
  • Scala
    • \\n
  • SCSS
    • \\n
  • SH
    • \\n
  • SQL
    • \\n
  • SVG
    • \\n
  • Text
    • \\n
  • Textile
    • \\n
  • XML
    • \\n
  • XQuery
    • \\n
  • YAML
    • \\n
\\n

We are always adding new themes and new languages to support, so check the menu often! Since we use Ace to provide syntax highlighting, feel free to log an issue there for new requests.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"uploading_downloading\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Uploading and Downloading Workspace Files\",\n \"contents\": \"\\n

Uploading and Downloading Workspace Files

\\n

Cloud9 IDE allows you to easily add files to your curent workspace at any time. You can drag and drop files from your computer directly into the Project Files pane, and the IDE will add them to your project. Google Chrome users can also drag entire folders into the IDE.

\\n

If a file transfer is halted for some reason--say, if you lose your internet connection--the upload resumes once the connection returns. As the files transfer, the IDE lets you know the current status of the overall transfer, as well as the status of each file being uploaded:

\\n

\\\"Uploading

\\n

You can also get an exact copy of your workspace to save on your computer. By going into File > Download Project, you will be provided with a Zip file containing the entirety of your project.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_drupal\",\n \"mtime\": 1416998221000,\n \"pageTitle\": \"Framework: Drupal\",\n \"contents\": \"\\n

Framework: Drupal

\\n

For Drupal there are some installation guides around which tell you to install PHP first, but that's not necessary with Cloud9.\\nYou don't need to install MySQL either, it is already preinstalled in PHP workspaces. \\nJust make a new workspace, choose PHP, go to the Terminal, and execute the following:

\\n
cd $HOME\\ncurl -O http://ftp.drupal.org/files/projects/drupal-7.30.tar.gz\\ntar xvf drupal-7.30.tar.gz\\nmv drupal-7.30/* workspace/\\nmv drupal-7.30/.htaccess workspace/\\ncd $HOME/workspace\\nmysql-ctl install\\nmysql-ctl start\\nmysql-ctl status
\\n

Open the file install.php in the file tree, and while opened, click on the "Run Project" button in the menu bar on top of the IDE.\\nAn URL will be shown at the bottom of the page, something like "https://drupal-c9-lcipriani.c9.io/", but with your username and workspace name in it.

\\n

Copy the url in a new browser tab and you will see the install page of Drupal

\\n

You can now proceed with the installer

\\n

\\\"Drupal

\\n

Now be careful inserting the correct values for the database. You need to change the values as follows:

\\n
user: yourusername\\ndatabase: c9\\nhost: 127.0.0.1
\\n

Note:

localhost will not work, while 127.0.0.1 will.\\n\\n
\\n

Open the Advanced Options in the database settings page as shown in the screenshot:

\\n

\\\"Drupal

\\n

Now fill the form with the correct site information:

\\n

\\\"Drupal

\\n

Continue the setup and enjoy your website!

\\n

Note:

if you are not able to load CSS, access your website WITHOUT using https, but use simple http; in another tab open the url: http://drupal-c9-lcipriani.c9.io/\\n\\n
\\n

\\\"Drupal

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"git_blame\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Git Blame\",\n \"contents\": \"\\n

Git Blame

\\n

Note:

this feature is deprecated\\n\\n
\\n
\\n\\n
\\n\\n

When you're working with git repositories, it's helpful to know who made a commit to a particular piece of code. As it turns out, git has a feature called git blame that we've integrated directly into Cloud9 IDE.

\\n

By using git blame, you'll be able to instantly discover who edited certain lines of code, when they edited it, and what their commit message at the time was. Clicking on a git commit also highlights other lines of code changed at the same time. To launch the git blame feature, open a file and navigate to Tools > Git > Blame.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"zen_mode\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Activating Zen Mode\",\n \"contents\": \"\\n

Activating Zen Mode

\\n

Note:

this feature is deprecated\\n\\n
\\n
\\n\\n
\\n\\n

Zen mode is a full screen coding environment designed to make you more productive. It essentially removes all the additional UI elements in Cloud9 IDE, and places you in a harmonious relationship with your code.

\\n

To activate zen mode, simply hover over the upper right corner of the code editor, and click the icon that appears. Keep in mind that you'll need to have a file open before you can launch zen mode. You can resize your window by holding and dragging the left or right border.

\\n

To get out of zen mode, hover over the same corner and click the same icon.

\\n

You can also enter and exit zen mode via keyboard shortcuts, command line, or from the menu bar at View > Zen Mode.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_ionic\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Framework: Ionic\",\n \"contents\": \"\\n

Framework: Ionic

\\n

Ionic is an open source front-end framework for developing hybrid mobile apps with HTML5.

\\n

Create a Ionic app as follows:

\\n
    \\n
  1. Create a new workspace (Node.js or Custom for a clean workspace)
    2. \\n
  2. Open a Terminal, or use the pre-existing one at the bottom
    3. \\n

  3. Run the following commands in the Terminal:

    \\n
     $ npm install -g cordova ionic\\n $ ionic start myApp sidemenu\\n $ cd myApp\\n $ ionic serve $PORT
    \\n
    4. \\n

  4. Click the "Preview" button in the top menu in the IDE, and choose "Preview with Web Server". This will open the Preview window for your running app.

    \\n
    5. \\n
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_ghost\",\n \"mtime\": 1416995769000,\n \"pageTitle\": \"Framework: Ghost\",\n \"contents\": \"\\n

Framework: Ghost

\\n

Ghost is a simple, powerful publishing platform that \\nallows you to share your story with the world.

\\n

Create a Ghost blog as follows:

\\n
    \\n
  1. Create a new workspace (Node.js or Custom for a clean workspace)
    2. \\n
  2. Open a Terminal, or use the pre-existing one at the bottom
    3. \\n

  3. Run the following commands in the Terminal:

    \\n
     $ curl -L https://ghost.org/zip/ghost-latest.zip -o ghost.zip\\n $ unzip -uo ghost.zip -d .\\n $ rm ghost.zip\\n $ npm install --production
    \\n
    4. \\n

  4. Adapt the config.js file to the Cloud9 environment. Change the following keys:

    \\n
     config: {\\n     development: {\\n         url: 'https://' + process.env.C9_HOSTNAME,\\n     },\\n     server: {\\n         host: process.env.IP,\\n         port: process.env.PORT\\n     }\\n }
    \\n
    5. \\n

  5. Run Ghost by typing npm start in the console or by opening index.js and\\nhitting the run button.

    \\n
    6. \\n
  6. Click the "Preview" button in the top menu in the IDE, and choose \\n"Preview with Web Server". This will open the Preview window for your newly setup Ghost blog
    7. \\n
\\n

Change the URL to /ghost and create your admin user to login to the Ghost admin interface

\\n

Note:

These instructions are based on the official Ghost Installation Guide\\n
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_joomla\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Joomla\",\n \"contents\": \"\\n
\\n

Joomla

\\n

Joomla is a popular open source CMS. \\nInstalling Joomla is very straightforward, but there are just a few quirks to keep in mind, which we describe below.

\\n

Note:

all instructions here are based on Joomla v3.x.\\n\\n
\\n

Download Joomla

\\n
    \\n
  1. Create a Cloud9 workspace of type "Custom" or "PHP"
    2. \\n

  2. Download and Unzip Joomla from the Terminal. You can find the latest version on the Joomla website

    \\n
     wget http://joomlacode.org/gf/download/frsrelease/19665/160049/Joomla_3.3.3-Stable-Full_Package.zip\\n unzip Joomla*.zip\\n rm Joomla*.zip
    \\n
    3. \\n
\\n

Start the database

\\n

Joomla requires a MySQL database to connect to. MySQL is pre-installed in your workspace, so just execute these commands:

\\n
mysql-ctl install\\nmysql-ctl start
\\n

... and then note the credentials to use in the configuration of Joomla later on.

\\n

Install Joomla

\\n

To run the Joomla installer, open index.php and run it with the "Run" (or "Run Project") button at the top of the IDE.\\nNext, click the URL that's displayed in the Run panel, which looks something like https://joomla-c9-username.c9.io/installation/index.php#. \\nThis will open up the Preview window with the installer.

\\n

Now, here comes the quirky part: the installer will not work properly if it's loaded over HTTPS, as the Cloud9 Preview window does by default.\\nSo, in order to make the Joomla installer work, do the following:

\\n
    \\n
  1. Pop out the Preview by clicking the Popout icon \\\"Preview (or copy & load the URL in a browser tab)
    2. \\n
  2. Change the URL from https:// to http:// and load it
    3. \\n
\\n

Now you should be able you to get through the installer successfully.

\\n

Main configuration

\\n

The main Configuration screen should look like this:

\\n

\\\"Joomla

\\n

Enter whatever values you'd like here.

\\n

Database

\\n

The second quirky and important thing to keep in mind in the Database section, is to use Host Name "0.0.0.0" instead of "localhost".

\\n

So use values like shown in the screenshot below:

\\n

\\\"Joomla

\\n

Finally

\\n

Use whatever settings you'd like in the final installation screen, and after it completes, have Joomla remove the Installation folder for safety.

\\n

That's it, you're done and your Joomla setup should run fully on Cloud9!

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"revisions\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Revisions\",\n \"contents\": \"\\n

Revisions

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n
\\n\\n
\\n\\n

Every time you save a file on Cloud9, a diff of any changes made to it is saved by the server. Over time, you can view these file revisions as content is added and removed from your files. You can also restore a file to any previously saved state; you'll never have to worry about losing your work ever again!

\\n

To access file revisions, you can either go to File > File Revisions History, or type Cmd-B on Mac or Ctrl-B on Linux/Windows. This will pop open the Revisions History panel. Red lines indicate lines that were removed; green lines indicate lines that were either added or changed.

\\n

At the bottom of the panel, there's a checkbox for showing all of a file's changes. Files changes that occur relatively soon to one another--say, a few seconds--are grouped by the revisions panel as one "change." If you prefer to see every single change as an individual entry, enable the Show all file changes checkbox.

\\n

To restore a file to a previous revision, simply click the revisions button for that entry: \\\"Revisions

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_koa\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Framework: Koa\",\n \"contents\": \"\\n

Framework: Koa

\\n

Koa is a new web framework designed by the team behind Express, which aims to be a smaller, more expressive, and more robust foundation for web applications and APIs.

\\n

To get started with a Koa app, first create a workspace and choose either the Node.js type, or a Custom workspace type for a clean workspace.

\\n

Koa.Js makes use of the new generator feature in javascript ECMA 6. \\nThis feature is support in Node from 0.11 and up by toggling the --harmony flag. \\nBy default Cloud9 runs Node v0.10.x or v0.8.x, depending on your setup, so we first need activate Node version 0.11.x.

\\n

Open a Terminal, or using the pre-existing one at the bottom and execute the following in your Terminal:

\\n
nvm use 0.11
\\n

Next, we need to install Koa itself:

\\n
npm install koa
\\n

Now we can create a simple Koa.Js server.\\nCreate a server.js file in your root folder with this code:

\\n
var koa = require('koa');\\nvar app = koa();\\n\\napp.use(function *(){\\n    this.body = '<h1>Hello from Koa.Js</h1>';\\n});\\n\\napp.listen(process.env.PORT);
\\n

If you now press the Run button on top of the IDE, you will see some errors, as the runner/debugger defaults to 'Node (default)', which is Node version 0.10.x or 0.8.x.

\\n

Luckily all you need is to create a Runner file so Cloud9 can run Node 11.x in harmony mode and thereby support generators.

\\n

In the Run panel below, click the 'Runner' text input and choose 'New Runner'. \\nIn the new Runner file that's opened, save the following code as 'Node 0.11.x.run':

\\n
// This file overrides the built-in Node 0.11.x runner\\n// For more information see http://docs.c9.io:8080/#!/api/run-method-run\\n{\\n  \\\"cmd\\\": [\\n    \\\"bash\\\",\\n    \\\"--login\\\",\\n    \\\"-c\\\",\\n    \\\"nvm use 0.11 > /dev/null; node --harmony ${debug?--nocrankshaft --nolazy --debug-brk=15454} '$file' $args\\\"\\n  ],\\n  \\\"debugger\\\": \\\"v8\\\",\\n  \\\"debugport\\\": 15454,\\n  \\\"info\\\": \\\"Your code is running at \\\\\\\\033[01;34m$url\\\\\\\\033[00m.\\\\n\\\\\\\\033[01;31mImportant:\\\\\\\\033[00m use \\\\\\\\033[01;32mprocess.env.PORT\\\\\\\\033[00m as the port and \\\\\\\\033[01;32mprocess.env.IP\\\\\\\\033[00m as the host in your scripts!\\\\n\\\"\\n}
\\n

Note:

alternatively, you can check 'Show Hidden Files' in your workspace directory tree (the small gear in the upper right corner), and create a new file in the '.c9/runners' folder called 'Node 0.11.x.run' with this code.\\n\\n
\\n

Let's run server.js with this new configuration; in the Run panel on the bottom, choose your new 'Node 0.11.x' Runner, and press Run again.

\\n

You Koa.Js server should now be up and running.

\\n

Now if you click the Preview button in the top menu in the IDE, and choose "Preview with Web Server", this will open the Preview window for your running app.

\\n

(Credits go to Tom at http://kyorcode.blogspot.nl/2014/08/running-koajs-in-cloud9.html)

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_express\",\n \"mtime\": 1416998221000,\n \"pageTitle\": \"Framework: Express\",\n \"contents\": \"\\n
\\n

Framework: Express

\\n

Express is a minimal and flexible Node.js web application framework that provides a robust set of features for web and mobile applications.

\\n

To get started with an Express app, first create a workspace and choose either the Node.js type, or a Custom workspace type for a clean workspace. Open the new workspace (or an existing one) to follow the instructions below.

\\n

Installation

\\n

First we'll install the Express project generator and generate an application stub:

\\n
$ npm install -g express-generator\\n$ express -f .\\n$ npm install
\\n

You might want to take a look at package.json and update the application name from the default workspace to something more fitting.

\\n

Running

\\n

Now you have a fully configured express application already. You can run it from the terminal using:

\\n
$ bin/www
\\n

Now if you click the Preview button in the top menu in the IDE, and choose "Preview with Web Server", this will open the Preview window for your running app.

\\n

Creating a Run Configuration

\\n

In order to make life easier you can create a run configuration for express.

\\n
    \\n
  1. Click Run -> Run Configurations -> Manage ...
    2. \\n
  2. Click Add New Config
    3. \\n
  3. In the run panel fill in Express as name, bin/www as the command and Node 0.10.x as the runner.
    4. \\n
  4. You can optionally make this run configuration the default runner by clicking Set As Default. If you do so then clicking the run button will always run the app and not the currently opened file.
    5. \\n
\\n

The finished run configuration should look something like this

\\n

\\\"Express

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_laravel\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Framework: Laravel\",\n \"contents\": \"\\n

Framework: Laravel

\\n

For Laravel there are some installation guides around which tell you to install PHP first, but that's not necessary with Cloud9.\\nJust make a new workspace, choose PHP, go to the Terminal, and execute the following:

\\n
rm README.md php.ini hello-world.php\\ncomposer create-project laravel/laravel ./laravel --prefer-dist\\nshopt -s dotglob\\nmv laravel/* ./\\nrm -rf laravel
\\n

As lavarel is serving its content from the public directory we need to modify the apache config:

\\n
sudo vi /etc/apache2/sites-enabled/001-cloud9.conf
\\n

Then do the following:

\\n
// Change this line\\nDocumentRoot /home/ubuntu/workspace\\n\\n// To following\\nDocumentRoot /home/ubuntu/workspace/public
\\n

Run the project with the "Run Project" button in the menu bar on top of the IDE.\\nIf you click the URL that appears in the Run panel below (in the shape of 'https://laravel-c9-username.c9.io/'), you can preview your new Laravel app.

\\n

\\\"Run

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_meteor\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Framework: Meteor\",\n \"contents\": \"\\n

Framework: Meteor

\\n

Meteor is an open-source platform for building web apps.

\\n

Create a Meteor app as follows:

\\n
    \\n
  1. Create a new workspace (Node.js or Custom for a clean workspace)
    2. \\n
  2. Open a Terminal, or using the pre-existing one at the bottom
    3. \\n

  3. Run the following commands in the Terminal:

    \\n
     curl https://install.meteor.com/ | sh\\n meteor create ./my_cool_app\\n cd my_cool_app/\\n meteor --port $IP:$PORT
    \\n
    4. \\n

  4. Click the Preview button in the top menu in the IDE, and choose "Preview with Web Server". This will open the Preview window for your running app.

    \\n
    5. \\n
\\n

Note:

Alternatively, for the last step, click on the link that's displayed in the terminal, and change it in the resulting Preview to http://127.0.0.1:8080.
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_symfony2\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Framework: Symfony2 \",\n \"contents\": \"\\n
\\n

Framework: Symfony2

\\n

Symfony is one of the leading PHP Webframeworks. It is Open-Source and built on top of the Symfony Components.

\\n

Getting started

\\n
    \\n
  1. Create a Cloud9 workspace of the type "Custom" or "PHP"
    2. \\n

  2. Install the Intl extension for PHP that is required in most of the Symfony2 projects

    \\n
     sudo apt-get install php5-intl
    \\n
    3. \\n

  3. Set a valid PHP timezone

    \\n
     echo 'date.timezone = UTC' | sudo tee --append /etc/php5/apache2/php.ini
    \\n
    4. \\n

  4. Starting MySQL-Server

    \\n
     sudo mysql-ctl install\\n sudo mysql-ctl start
    \\n
    5. \\n
\\n

Create a Symfony-Project

\\n

Open your Terminal and execute the following to create a new Symfony-Project\\nYou need the first line only if you used the PHP Project type for your workspace.

\\n
    rm README.md php.ini hello-world.php\\n    composer create-project symfony/framework-standard-edition symfony/ \\\"2.5.*\\\"\\n    mv symfony/{*,.*} ./ \\n    rm -rf symfony
\\n

The create-project composer command will ask for a few parameters, the only one you need to pay special attention is the database-host parameter.

\\n

Running the project

\\n

There is a IP address checking in the web/app_dev.php file. To disable this check please remove the following lines

\\n
    // This check prevents access to debug front controllers that are deployed by accident to production servers.\\n    // Feel free to remove this, extend it, or make something more sophisticated.\\n    if (isset($_SERVER['HTTP_CLIENT_IP'])\\n        || isset($_SERVER['HTTP_X_FORWARDED_FOR'])\\n        || !in_array(@$_SERVER['REMOTE_ADDR'], array('127.0.0.1', 'fe80::1', '::1'))\\n    ) {\\n        header('HTTP/1.0 403 Forbidden');\\n        exit('You are not allowed to access this file. Check '.basename(__FILE__).' for more information.');\\n    }
\\n

After that add a new run configuration in Menu Run > Run Configurations > New Run Configuration. Select Apache http (PHP, HTML) as a Runner and web/app_dev.php as Command.\\nThat's it after you hit Run your server will start up and you can access your new Symfony project.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"run_an_application\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Run an application\",\n \"contents\": \"\\n
\\n

Run an application

\\n

On Hosted and SSH workspaces, Cloud9 provides two ways to run your application:

\\n
    \\n
  1. Using the Run panel with built-in Runners for many languages
    2. \\n
  2. From a Terminal
    3. \\n
\\n

Method 1: Use the Run panel

\\n

First, open the file you want to run.

\\n

Next, click on the Run button in the top menu bar in the IDE.

\\n

\\\"Run

\\n

The Run button acts as a sort of shortcut to the Run panel, which will appear by default in the bottom of the IDE when you run a file.\\nThis automatically runs the currently active file, and it will guess which Runner to use based on the extension of the file.

\\n

When you're ready to stop your app, click on the Stop Button button in the menu bar at any time, or from the Run panel below.

\\n

\\\"Run

\\n

On the Run panel, you'll notice a few more options you can set. \\nFilling these textboxes out creates a Run Configuration.

\\n
    \\n
  • Name: the name of your run scenario
    • \\n
  • Command: the command you want to run; this is usually the location of your running file in your project, but it also allows you to provide any additional command line arguments you want to pass to your app
    • \\n
  • Runner: defines how you want your code to be run. A wide range of Runners is available by default, from Apache to Node.js and Shell scripts, and you can define your own.
    • \\n
  • CWD: Set the current working directory to start from
    • \\n
  • Environment: Set environment variables
    • \\n
  • \\n
\\n

Tip:

If you can't find the Runner you need from the default set, you can create your own custom Runner.\\n\\n
\\n

For some default runners like Node.js, it's an option to Run in debug mode, which indicates that you want to run the current code through the debugger. \\nThis will reveal (or collapse) the debugging tools panel described in Running and Debugging your code.

\\n

Method 2: From the Terminal

\\n

The built-in Terminal provides access to all underlying system commands, including your Runners such as Node.js. \\nSimply open up a Terminal from the "+" sign, or use CMD+T (Mac) / Control+T (Windows), and then execute the command you need to run your app, e.g. node server.js.

\\n

(Pre-)View your application

\\n

To find out where your application is running you can do two things:

\\n
    \\n
  1. Use the Preview button on the top to preview one of your files. The URL in the browser bar in the Preview can also be used in any browser tab/window.
    2. \\n
  2. Use the Share button on the top to figure out the URLs of running Application and the Preview. The Editor URL is only used to share your entire Cloud9 workspace to collaborate on code.
    3. \\n
\\n

Tip:

If you can't find how to preview your running app, try to use port 8080 in the URL.
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setup_a_database\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Set up a database\",\n \"contents\": \"\\n
\\n

Set up a database

\\n

MySQL

\\n

From the Terminal, run the following command:

\\n
$ mysql-ctl install
\\n

The output will be:

\\n
MySQL 5.5 database added.  Please make note of these credentials:\\n\\nRoot User: username\\nDatabase Name: c9
\\n

Now you can connect to the database using the ip 127.0.0.1 and the default port 3306.\\nYou can also test it using our tool from the Terminal:

\\n
$ mysql-ctl cli\\nWelcome to the MySQL monitor.  Commands end with ; or \\\\g.\\nYour MySQL connection id is 24\\nServer version: 5.5.37-0ubuntu0.14.04.1 (Ubuntu)\\n\\nCopyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved.\\n\\nOracle is a registered trademark of Oracle Corporation and/or its\\naffiliates. Other names may be trademarks of their respective\\nowners.\\n\\nType 'help;' or '\\\\h' for help. Type '\\\\c' to clear the current input statement.\\n\\nmysql>  show databases;\\n+--------------------+\\n| Database           |\\n+--------------------+\\n| information_schema |\\n| c9                 |\\n| mysql              |\\n| performance_schema |\\n+--------------------+\\n4 rows in set (0.15 sec)
\\n

MongoDB

\\n

From the Terminal, run the following command:

\\n
$ mongod --bind_ip=$IP --nojournal
\\n

The output will include:

\\n
...\\nwaiting for connections on port 27017
\\n

Now you can open the mongo shell in a new Terminal, running following command:

\\n
$ mongo
\\n

To stop the MongoDB instance press Control+C in the Terminal where mongod is running.\\nNow have a look at the currently used database:

\\n
$ mongo\\nmongo> db\\ntest
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"dashboard\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"The Dashboard\",\n \"contents\": \"\\n

The Dashboard

\\n

After you have logged into Cloud9, you are placed into your account's dashboard. From here, you can edit your profile and manage workspaces you have access to.

\\n

\\\"An

\\n

In the top-left corner of the dashboard, your username is displayed. Within the user context, you can view your user profile by clicking on Your Account:

\\n

\\\"A

\\n

The user profile contains:

\\n
    \\n
  • Your recent activities, including a list of actions you have recently performed, such as cloning, opening, and deleting projects
    • \\n
  • Your add-on services, which you've integrated into Cloud9. Currently, these are GitHub and Bitbucket.
    • \\n
  • Your account settings, where you're given the following choices:
      \\n
    • Change your password
      • \\n
    • Show your SSH key
      • \\n
    • Upgrade to premium (or, downgrade from it)
      • \\n
    • Delete your account
      • \\n
    \\n
    • \\n
\\n

The gravatar that is used for your profile is handled by gravatar.com. If you don't have a gravatar yet, Cloud9 IDE uses an uninspiring default.

\\n

In the left panel, you'll find a list of various projects associated with your account. These are:

\\n
    \\n
  • My Projects: these are projects you've created or cloned, and own
    • \\n
  • Shared With Me: these are projects shared with you by other Cloud9 users
    • \\n
  • Recently Visited: these are projects you've seen lately
    • \\n
  • Projects on GitHub: a list of your uncloned public and private GitHub projects
    • \\n
  • Projects on Bitbucket: a list of your uncloned public and private Bitbucket projects
    • \\n
\\n

Clicking on the \\\"Project next to MY PROJECTS lets you:

\\n
    \\n
  • Create a new project
    • \\n
  • Clone from URL
    • \\n
\\n

\\\"Creating

\\n

For more information on creating new workspaces, see this section of the documentation.

\\n

You can always filter your project list by entering text in the text bar to find matching projects. If you need to update the list, click the refresh icon at the bottom of the panel: \\\"Refresh

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"create_a_workspace\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Create a Workspace\",\n \"contents\": \"\\n

Create a Workspace

\\n

Cloud9 supports three types of workspaces:

\\n
    \\n
  1. Hosted
    2. \\n
  2. FTP
    3. \\n
  3. SSH
    4. \\n
\\n

"Hosted" is the best choice for most people, so in this short "Getting Started" article we'll only describe this option; for other options please read the full Creating a new workspace article.

\\n

The first step for creating a new workspace is click the "CREATE NEW WORKSPACE" button in your Dashboard:

\\n

\\\"New

\\n

At this point, you'll encounter two choices: Create a new workspace and Clone from URL. \\nIn this article we'll only describe the Create a New Workspace option, which allows you to create any of the previously mentioned types of workspaces (hosted, FTP, or SSH).

\\n

After clicking on Create a new workspace, you're taken to the screen below:

\\n

\\\"Options

\\n

First, let's enter a workspace name.\\nDepending on whether you have a Free of Premium account, you can choose to make it either Public (open to anyone with the URL), or Private (only accessible to you and people you share it with).

\\n

After this, choose the type of workspace you want to create:

\\n\\n

Choose the "Hosted" workspace type to start from scratch with a 'Custom' workspace, or simply pick a pre-configured environment like Node.js, WordPress, or Python/Django, and immediately start developing your app.\\nThis way you don't need to spend valuable development time on system setup and maintenance, as we maintain it, and you control it.

\\n

\\\"Options

\\n

As it's powered by a full Linux Ubuntu environment, hosted workspaces allow you to install any package (sudo apt-get install package), run git commands from the console to push your changes to a GitHub repo or a Bitbucket git repo, etcetera.

\\n

Now press Create. That's it! You can now see your new workspace in the dashboard:

\\n

\\\"New

\\n

Now, just click Start Editing to get started!

\\n

Next up, read how to run an application and set up a database.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"ide_overview\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"IDE Overview\",\n \"contents\": \"\\n
\\n

IDE Overview

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n

Cloud9 IDE can be thought of as being divided into the following components:

\\n

\\\"IDE

\\n

Throughout the documentation, we'll refer to these sections by name. We can identify several distinct areas in the editor:

\\n
    \\n
  • The top menu bar is the uppermost area, with easy access to a variety of menus
    • \\n
  • The project bar on the left lets you manipulate various aspects of your project, including its active files, preferences, and choices for deployment
    • \\n
  • The panel displays views according to what's been selected in the project bar
    • \\n
  • The toolbar is on the far right, where you can find tools used when debugging your code. Projects that are open with collaboration also make use of this panel for chatting.
    • \\n
  • The code editor is the main area where you write your code.
    • \\n
  • The console is the bottom area of the window. It's an expandable area that can act like a desktop terminal to enter command line input (like ls or mkdir). It also displays output provided by your program's print statements (like console.log()), as well as providing an area for search results
    • \\n
\\n

The Project Bar, Tool Bar, and Console are powerful features, so their documentation is provided separately. We'll talk about the rest of the editor below:

\\n

Remember: nearly every UI element can be collapsed, in order to provided a more harmonious coding experience. For example, clicking on the buttons in the upper left of the editor allows you to hide the panels and top menu bar:
\\\"Hiding

\\n

The Top Menu Bar

\\n

\\\"A

\\n

In this section, you can find the usual menus for creating and saving files, changing your view, applying a new theme for the editor, and switching between windows.

\\n

In the middle of the menu bar you'll find the debug button: \\\"The. This is used for running and debugging your code. For more information, see the section on "Running and Debugging Your Code"..

\\n

\\n

The preview button \\\"The provides you with a look of what the currently active file would look like in the browser. For text files, this is usually just the raw text, but certain files, like HTML or XML, render as the actual markup.

\\n

The autosave button indicates the status of your current saves: \\\"Autosave. Files are saved automatically by Cloud9 IDE, and every revision is made available for you to browse through. For more information, see the section on revisions and saving.

\\n

On the far right of the menu, near the Cloud9 IDE logo, there are two more icons: one to return to the dashboard, and one to return to the Cloud9 IDE homepage.

\\n

The Code Editor

\\n

This is where most of the action happens. Every file you open appears here as a tab. You can open a new file easily by clicking on the \\\"Tab button to the right of the last tab. Cloud9 IDE offers syntax highlighting for over two dozen programming languages.

\\n

The code editor supports a large number of keyboard shortcuts to increase your productivity. For an up-to-date list of these within the IDE, simply go to Help > Keyboard Shortcuts.

\\n

If you hover over to the upper-right corner, you can activate zen-mode, which is a full screen coding environment.

\\n

At the lower-right corner, you can find the status bar.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"share_a_workspace\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Share a workspace\",\n \"contents\": \"\\n
\\n

Share a workspace

\\n

As you develop your application, often you just want to quickly demo your work-in-progress to a colleague, customer, or friend. \\nOr you want to pull in a fellow dev to debug an issue, or to pair program.

\\n

Cloud9 enables you to do just these things, easily: share your entire development environment, the running application, or just a preview of your running application. \\nHere we describe how to access these options, and how to use each.

\\n

Share dialog

\\n

The best place to start sharing is from the dedicated "Share" dialog. \\nAccess it via the "Share" button on the right top of the IDE, or via the menu in Window > Share...

\\n

\\\"Share

\\n

Here's what you see when you pull up the Share dialog:

\\n

\\\"Share

\\n

Links to share

\\n
    \\n
  • Editor: see section "Share your development environment"
    • \\n
  • Application: see section "Share your application"
    • \\n
  • \\n
\\n

If you enable the "Public" checkbox for an option, it will make the URL accessible for anyone with the URL.\\nFor public workspaces all these URLs are public by default, but for private workspaces you have to enable them manually.

\\n

Who has access

\\n

This section refers to people you have specifically granted access to your entire development environment.\\n(R) gives Read access only to that person: the ability to open and view files, and to run your code.\\n(RW) or "Read/Write" also gives that person the ability to write to files.

\\n

Invite people

\\n

This section enables you to invite people to your workspace and immediately set if they have just "Read" or "Read+Write" rights. \\nYou can invite people by their email address or Cloud9 username. \\nYou can also choose whether or not send an automatic email to that person that they've been invited to your workspace.

\\n

Share your development environment

\\n

Cloud9's Collaboration features allow you to share your entire development environment so you can work on code together, much like working on a document in Google Docs.\\nYou'll actually be able to see each other's cursor as you type, run your app, share the Terminal(s), and talk in the group chat.\\nSee the screenshot below for what this looks like:

\\n

\\\"Collaboration

\\n

In order to share your entire development environment, do one of the following:

\\n
    \\n
  1. Make the URL publicly available to everyone: check the "Public" checkbox for the "Editor" in the "Links to Share" section.
    2. \\n
  2. Choose to share only with specific people: invite them from the "Invite people" section.
    3. \\n
  3. Grant/revoke access rights in the "Who has access" section.
    4. \\n
\\n

If someone asks for either Read or Read+Write access to your workspace, you can accept or deny them from the Collaboration panel on the right.

\\n

Note:

alternatively you can just share the URL to your workspace from the browser's URL bar and accept members as they request access to your workspace\\n\\n
\\n

Share your application

\\n

If you Run your application the result can be shared by copying the URL from the dialog. \\nThis URL can only be viewed if it's made Public by checking the "Public" checkbox next to the "Application" in the "Links to share" section.

\\n

People who have full read access to your workspace (as defined in the "Who has access") can view this URL whether it's public or not.

\\n

Note:

alternatively you can just share the URL to your running app from the Preview panels' URL bar\\n\\n
\\n

Share a Preview

\\n

If you Preview a file in your application, it can be shared by copying the URL from the dialog. \\nThis URL can only be viewed if it's made Public by checking the "Public" checkbox next to the "Preview" in the "Links to share" section.

\\n

People who have full read access to your workspace (as defined in the "Who has access") can view this URL whether it's public or not.

\\n

Note:

alternatively you can just share the URL to your Preview from the Preview panels' URL bar\\n\\n
\\n

Tip:

If you can't find how to preview your running app, try to use port 8080 in the URL.
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"console\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"The Console\",\n \"contents\": \"\\n
\\n

The Console

\\n

Note:

this feature is deprecated\\n\\n
\\n

The Console is at the bottom of the IDE. It's where you can enter command line input, view output from your program, and push and pull your files between your code repositories.

\\n

Note:

The Console contains a full-fledged terminal, which provides you with a TTY interface for direct access to the machine that Cloud9 is running on.\\n\\n
\\n

Available Commands

\\n

The terminal can perform all Unix commands, and allows for path autocompletion by hitting Tab.

\\n

For instance, you can use mercurial commands (hg) and git commands (git) to communicate with the system, and to push your code between repositories. Typing hg or git shows the complete list of commands that are available for these services. For more information about these commands, please check their respective documentation:

\\n\\n

To use mercurial commands on the project you are working on, you must have a mercurial project set up; the same holds true for git. Follow these links to learn more about how to set up these project in Cloud9:

\\n\\n

Output

\\n

The output tab in the Console shows information whenever a user is running or debugging a program. The content is similar to the output of a desktop terminal:
\\\"Screenshot

\\n

The output tab also displays the error and additional information that can improve your coding quality. You can use the Console to output results from your running application, just like a regular terminal.

\\n

As your process runs, you'll see a message similar to this one indicating that Cloud9 is running something in the background: \\\"Running

\\n

If you hover over this message, you can opt to cancel the process by clicking on the button: \\\"Cancelling

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_angularjs\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Framework AngularJS\",\n \"contents\": \"\\n

Framework AngularJS

\\n

AngularJS lets you write client-side web \\napplications as if you had a smarter browser.

\\n

Follow these steps to create an AngularJS application using the official project\\ntemplate:

\\n
    \\n
  1. Create a workspace and choose the PHP workspace type
    2. \\n
  2. Open a Terminal, or using the pre-existing one at the bottom
    3. \\n
  3. Run the following commands in the Terminal:
    rm -rf * .c9\\ngit clone https://github.com/angular/angular-seed.git .\\nnpm install\\nmv package.json package.json.bak\\njq '.scripts.start=\\\"http-server -a $IP -p $PORT\\\"' package.json.bak > package.json
    \\n
    4. \\n
  4. Click the Run Project button in the top menu of the IDE
    5. \\n
  5. Check the README.md for further steps
    6. \\n
\\n

Note:

We are choosing the PHP workspace type to in order to have the Apache runner\\nas a default so you can just click Run Project to get started. This doesn't\\nlimit the choice of the backend technology you might want to use.
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"keybindings\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Commands and Keybindings\",\n \"contents\": \"\\n

Commands and Keybindings

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n

Nearly every action in Cloud9 has a corresponding command associated with it. On top of that, every command also has a keybinding that can be used to effortlessly execute the command.

\\n

Below is a list of every single command and keybinding used by Cloud9. Have fun being efficient!

\\n
\\n \\n
\\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
Command NameKeybinding
Abortclicommand˄-C
AddCursorAbove˄-⌥-Up
AddCursorAboveSkipCurrent˄-⌥-⇧-Up
AddCursorBelow˄-⌥-Down
AddCursorBelowSkipCurrent˄-⌥-⇧-Down
Backspace˄-⌫
Beautify⌘-⇧-B
Clearcut⎋
Closeallbutme⌥-˄-W
Closealltabs⌥-⇧-W
Closetab⌥-W
Complete˄-Space
Copy⌘-C
Copylinesdown⌘-⌥-Down
Copylinesup⌘-⌥-Up
Cut⌘-X
DelDelete
DuplicateSelection⌘-⇧-D
Escapeconsole⎋
EvalInteractive⌘-Return
Find⌘-F
Findnext⌘-G
Findprevious⌘-⇧-G
Fold⌘-⌥-L
Foldall⌘-⌥-0
GolinedownDown
GolineupUp
Gotoend⌘-End
Gotofile⌘-E
GotoleftLeft
Gotoline⌘-L
Gotolineend⌘-Right
Gotolinestart⌘-Left
GotopagedownPageDown
GotorightRight
Gotostart⌘-Home
Gototableft⌘-[
Gototabright⌘-]
Gotowordleft⌥-Left
Gotowordright⌥-Right
IndentTab
Jumptomatching˄-⇧-P
Largerfont˄-⇧-.
Movelinesdown⌥-Down
Movelinesup⌥-Up
Movetableft⌘-⌥-[
Movetabright⌘-⌥-]
Newfile⌥-⇧-N
Newfiletemplate⌥-˄-N
Newfolder⌥-˄-⇧-N
Nexttab⌥-Tab
Openfilepanel⇧-⌘-U
Opensettingspanel⌘-,
Opentreepanel⌘-U
Outdent⇧-Tab
Outline⌘-⇧-E
Paste⌘-V
Previoustab⌥-⇧-Tab
Quicksave⌘-S
Quickwatch⌥-Q
Redo⌘-⇧-Z
Removeline⌘-D
Removetolineend˄-K
Removetolinestart⌘-⌫
Removewordleft⌥-⌫
Removewordright⌥-Delete
RenameVar⌥-⌘-R
Replace⌥-⌘-F
Replaymacro⌘-˄-R
ResumeF8
Revealtab⇧-⌘-L
Reverttosaved˄-⇧-Q
Revisionpanel⌘-B
RunF5
Saveas⌘-⇧-S
Savetabsession⇧-˄-S
Searchinfiles⇧-⌘-F
SelectMoreAfter˄-⌥-Right
SelectMoreBefore˄-⌥-Left
SelectNextAfter˄-⌥-⇧-Right
SelectNextBefore˄-⌥-⇧-Left
Selectall⌘-A
Selectdown⇧-Down
Selectleft⇧-Left
Selectright⇧-Right
Selecttoend⌘-⇧-Down
Selecttolineend⌘-⇧-Right
Selecttolinestart⌘-⇧-Left
Selecttostart⌘-⇧-Up
Selectup⇧-Up
Selectwordleft⌥-⇧-Left
Selectwordright⌥-⇧-Right
Smallerfont˄-⇧-,
SplitIntoLines˄-⇧-L
StepintoF11
Stepout⇧-F11
StepoverF10
Stop⇧-F5
Switchconsole⇧-⎋
Tab0⌘-0
Tab1⌘-1
Tab2⌘-2
Tab3⌘-3
Tab4⌘-4
Tab5⌘-5
Tab6⌘-6
Tab7⌘-7
Tab8⌘-8
Tab9⌘-9
ToggleTabs˄-M
Togglecomment⌘-/
Toggleconsole˄-⎋
Togglerecording⌘-⇧-R
Tolowercase˄-⇧-U
Touppercase˄-U
Transposeletters˄-T
Undo⌘-Z
Unfold⌘-⌥-⇧-L
Unfoldall⌘-⌥-⇧-0
Zen⌥-Z
Zenslow⇧-⌥-Z
\\n
\\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
Command NameKeybinding
AbortclicommandCtrl-C
AddCursorAboveCtrl-Alt-Up
AddCursorAboveSkipCurrentCtrl-Alt-Shift-Up
AddCursorBelowCtrl-Alt-Down
AddCursorBelowSkipCurrentCtrl-Alt-Shift-Down
BackspaceCommand-Backspace
BeautifyShift-Ctrl-B
ClearcutESC
CloseallbutmeCtrl-Alt-W
ClosealltabsCtrl-Shift-W
ClosetabCtrl-W
CompleteCtrl-Space
CopyCtrl-C
CopylinesdownAlt-Shift-Down
CopylinesupAlt-Shift-Up
CutCtrl-X
DelDelete
DuplicateSelectionCtrl-Shift-D
EscapeconsoleEsc
EvalInteractiveCtrl-Return
FindCtrl-F
FindnextCtrl-K
FindpreviousCtrl-Shift-K
FoldAlt-L
FoldallAlt-0
GolinedownDown
GolineupUp
GotoendCtrl-End
GotofileCtrl-E
GotoleftLeft
GotolineCtrl-G
GotolineendAlt-Right
GotolinestartAlt-Left
GotopagedownPageDown
GotorightRight
GotostartCtrl-Home
GototableftCtrl-[
GototabrightCtrl-]
GotowordleftCtrl-Left
GotowordrightCtrl-Right
IndentTab
JumptomatchingCtrl-P
LargerfontCtrl-Shift-.
MovelinesdownAlt-Down
MovelinesupAlt-Up
MovetableftCtrl-Alt[
MovetabrightCtrl-Alt-]
NewfileCtrl-N
NewfiletemplateCtrl-Alt-N
NewfolderCtrl-N
NexttabCtrl-Tab
OpenfilepanelShift-Ctrl-U
OpensettingspanelCtrl-,
OpentreepanelCtrl-U
OutdentShift-Tab
OutlineCtrl-Shift-E
PasteCtrl-V
PrevioustabCtrl-Shift-Tab
QuicksaveCtrl-S
QuickwatchAlt-Q
RedoCtrl-Shift-Z
RemovelineCtrl-D
RemovetolineendAlt-Delete
RemovetolinestartAlt-Backspace
RemovewordleftCtrl-Backspace
RemovewordrightCtrl-Delete
RenameVarCtrl-Alt-R
ReplaceAlt-Shift-F
ReplaymacroAlt-R
ResumeF8
RevealtabCtrl-Shift-L
ReverttosavedCtrl-Shift-Q
RevisionpanelCtrl-B
RunF5
SaveasCtrl-Shift-S
SavetabsessionShift-Ctrl-S
SearchinfilesCtrl-Shift-F
SelectMoreAfterCtrl-Alt-Right
SelectMoreBeforeCtrl-Alt-Left
SelectNextAfterCtrl-Alt-Shift-Right
SelectNextBeforeCtrl-Alt-Shift-Left
SelectallCtrl-A
SelectdownShift-Down
SelectleftShift-Left
SelectrightShift-Right
SelecttoendCtrl-Shift-End
SelecttolineendAlt-Shift-Right
SelecttolinestartAlt-Shift-Left
SelecttostartCtrl-Shift-Home
SelectupShift-Up
SelectwordleftCtrl-Shift-Left
SelectwordrightCtrl-Shift-Right
SmallerfontCtrl-Shift-,
SplitIntoLinesCtrl-Shift-L
StepintoF11
StepoutShift-F11
StepoverF10
StopShift-F5
SwitchconsoleShift-Esc
Tab0Ctrl-0
Tab1Ctrl-1
Tab2Ctrl-2
Tab3Ctrl-3
Tab4Ctrl-4
Tab5Ctrl-5
Tab6Ctrl-6
Tab7Ctrl-7
Tab8Ctrl-8
Tab9Ctrl-9
ToggleTabsCtrl-M
TogglecommentCtrl-/
ToggleconsoleF6
TogglerecordingAlt-Shift-R
TolowercaseCtrl-Shift-U
TouppercaseCtrl-U
TransposelettersCtrl-T
UndoCtrl-Z
UnfoldAlt-Shift-L
UnfoldallAlt-Shift-0
ZenAlt-Z
ZenslowShift-Alt-Z
\\n
\\n
\\n
\\n
\\n
\\n \"\n },\n {\n \"filename\": \"the_editor\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"The Editor\",\n \"contents\": \"\\n

The Editor

\\n

The editor is the most important element of any IDE; that's why Cloud9 developed ACE. ACE is a high-performance code editor for the web that supports over 40 different languages, over two dozen themes, and can still work faithfully on large documents (at last count, four million lines of code was the upper limit). It also contains a bevy of features you'd expect from traditional desktop editors. Among these include:

\\n
    \\n
  • Undo and Redo support
    • \\n
  • Cut, Copy, and Paste functionality
    • \\n
  • Line manipulation, including:
      \\n
    • Indenting and outdenting
      • \\n
    • Moving and copying lines up or down
      • \\n
    • Removing lines from any point
      • \\n
    • Splitting lines
      • \\n
    \\n
    • \\n
  • Highlighting and commenting blocks of code
    • \\n
  • Removing words to the right or the left
    • \\n
  • Transposing letters
    • \\n
  • Code folding (including the entire file)
    • \\n
  • Converting cases
    • \\n
  • Multiple cursors
    • \\n
  • Autocompletion
    • \\n
  • Code analysis and refactoring
    • \\n
  • Search in files with regular expressions
    • \\n
  • Intelligent selections, including:
      \\n
    • Selecting to word right or left
      • \\n
    • Selecting to line end or start
      • \\n
    • Selecting to document end or start
      • \\n
    \\n
    • \\n
  • Vim and Emacs keybindings
    • \\n
  • Line wrapping, to a defined column or the width of the browser window
    • \\n
  • Support for a command line
    • \\n
  • Support for spaces and real tabs
    • \\n
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"ide_preferences\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"IDE Preferences\",\n \"contents\": \"\\n
\\n

IDE Preferences

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n

There are many different ways to configure the IDE. Below is a list of the options available, and what they do.

\\n

Note:

All of these options are on a per-project basis. Changing them in one project does not affect any another.\\n\\n
\\n

General

\\n

This section controls the overall IDE behavior:

\\n\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
Preference NameDescription
Enable UI AnimationsEnables or disables fluid animations for various UI elements, such as the Project Bar
Animate ScrollingEnables or disables fluid animations when scrolling through code (such as for goto line)
Enable Auto-SaveIf enabled, automatically saves your files on every change
On Save, Strip WhitespaceWhen saving a file, you can remove all extraneous whitespace from your code lines
Reveal Active File in Project TreeEnabling this jumps the project tree to the active file whenever a tab changes to a different file
Warn Before ExitingPrevents accidental data loss by showing a dialog asking if you really want to leave Cloud9 IDE when closing your browser
Node.js RuntimeDefines the default runtime for your Node.js code. "Auto" is based on whatever is in the package.json file, while "Default" reverts to Node 0.6.x.
KeybindingsAllows you to choose which operating system to use for keyboard shortcuts
\\n

Language Support

\\n

This section controls language analysis options:

\\n\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
\\n \\n \\n \\n \\n \\n \\n \\n
Preference NameDescription
Enable Hints and Warnings RulesPresents information about your code in the gutter
Highlight Variable InstancesHighlights variable instances in your code
Mark Undeclared VariablesProvides warnings if a variable is being used and has not been declared yet
Mark Unused Function ArgumentsProvides a strikethrough for arguments in a function that are not being used
Warning LevelSpecifies the minimum level of information severity you want provided in the gutter
\\n

Code Editor

\\n

This section controls language analysis options:

\\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
Preference NameDescription
Auto-pair Quotes, Brackets, etc.When enabled, typing ", (, or [ will actually make two characters appear. In addition, whenever you highlight a word and type one of these characters, it is surrounded by that character (e.g. words becomes "words")
Full Line SelectionWhen highlighting lines, this option will highlight all ending whitespace, until the end of the editor window
Highlight Active LinePresents a darker shade in the code editor to indicate which line you're currently on
Highlight Gutter LinePresents a darker shade in the gutter which line you're currently on
Show Invisible CharactersShows invisibles characters in the editor, like tabs and line breaks
Show Indent GuidesShows the indent guides in the editor, letting you see your code's nestings
Show GutterShows the gutter in the editor, which indicates line numbers, warnings, and errors
Highlight Selected WordIf you highlight a word, this highlights all matching words in the editor
Auto-hide Horizontal ScrollWhen this is enabled, this will hide the horizontal scroll bar in the editor. Note that this has no effect in Mac OS X 10.7 (Lion) and above, since all scrollbars, by default, auto-hide.
Vim ModeWhen enabled, allows you to use vim keybindings in the IDE
Code FoldingWhen enabled, allows you to show or hide "blocks" of code
Fade Fold WidgetsWhen enabled, fades the folding widgets in the gutter
Font SizeChanges the font size of the code in the editor
Show Print MarginShows (and defines) the number of characters possible in line, before it wraps
Soft TabsIndicates how many spaces a single tab represents
Mouse Scroll SpeedDefines the speed of the mouse scrolls
Newline ModeSpecifies the newline mode for the IDE
\\n

Terminal

\\n

This section controls the behavior for the terminal:

\\n
\\n \\n \\n \\n \\n \\n \\n \\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
\\n \\n \\n \\n
Preference NameDescription
ScrollbackSets the scrollback buffer for the terminal
Font FamilySets the font for the terminal
Font SizeSets the font size for the terminal
Blinking CursorSpecifies whether or not you want the cursor to blink
\\n

Code Tools

\\n

This section controls the various tools that are available in the IDE:

\\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n\\n \\n \\n
Preference NameDescription
Enable Color PickerMakes the color picker available for use
Preserve Empty LinesWhen enabled, the editor keeps any new lines without text
Keep Array IndentionWhen enabled, tabs and newlines in arrays are preserved. For example, the follow array would remain as-is with this option:\\n 
\\n        var o = [{\\n            a: b\\n        }, {\\n            c: d\\n        }];\\n
\\n
JSLint Strict WhitespaceIf selected, all brackets are preceded by a space. For example, if(x){ becomes if (x) {, and function(arg){ becomes function (arg) {
BracesThese options control how braces are handled in the IDE:\\n
    \\n
  • Braces with control statement: braces are left "in-line" alongside the code statements. For example, code is formatted like this:\\n 
    \\n    if (true) {\\n        var x = 3;\\n    } else {\\n        var x = 5;\\n    }\\n
    \\n
    • \\n
  • Braces on own line: braces are always placed on their own line. For example, code is formatted like this:\\n 
    \\n    if (true)\\n    {\\n        var x = 3;\\n    } else\\n    {\\n        var x = 5;\\n    }\\n
    \\n
    • \\n
  • End braces on own line: only the ending braces have their own line. For example, code is formatted like this:\\n 
    \\n    if (true) {\\n        var x = 3;\\n    }\\n    else {\\n        var x = 5;\\n    }\\n
    \\n
    • \\n
\\n
\\n
\\n
\\n \"\n },\n {\n \"filename\": \"terminal\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Terminal\",\n \"contents\": \"\\n

Terminal

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n

The terminal provides you with a TTY interface for direct access to the machine that Cloud9 is running on. If you're running your own workspace, this is the server you've SSH'ed into. If you're using the hosted Cloud9 platform, this is the server your code runs on.

\\n

Warning:

While certain operations, like sudo, are restricted, you can completely destroy your workspace, by doing something like rm -rf. Use your power wisely!\\n\\n
\\n

To create a new terminal, go to View > Terminals > New Terminal, or simply type Alt-T on the keyboard. The terminal has the following capabilities:

\\n
    \\n
  • Perform all Unix commands
    • \\n
  • You can create more than one instance of a terminal (by just creating a new tab)
    • \\n
  • The terminal allows for path autocompletion by hitting Tab
    • \\n
\\n

\\\"Screenshot

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_jekyll\",\n \"mtime\": 1416998221000,\n \"pageTitle\": \"Framework: Jekyll\",\n \"contents\": \"\\n

Framework: Jekyll

\\n

Jekyll is a great static site generator, also used by github pages. You simply need to install the Ruby gem and then make sure you pass the right port to the serve command.

\\n
$ gem install jekyll\\n$ jekyll new my-awesome-site\\n$ cd my-awesome-site\\n$ jekyll serve --port $PORT
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"index\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Cloud9 IDE User Documentation\",\n \"contents\": \"\\n

Welcome to the official Cloud9 IDE documentation! Here, you'll find articles and tutorials to help you use the Cloud9 platform. These include everything from setting up a workspace, to learning how to run, debug, and deploy your code.

\\n\\n\\n

Getting started

\\n

Have a look at the "Getting Started" section on the left for an introduction into the basics of Cloud9.\\nFor instance, read up on how to:

\\n\\n

Getting More Help

\\n

If you're interested in troubleshooting specific aspects of the IDE, need help setting up an account, or just want to chat with our support team, please visit the Support pages.

\\n

Contact Us

\\n

Remember: All of our documentation content is open-sourced on GitHub, just like our amazing IDE.

\\n

See something that's not documented here? Simply add it to the documentation with a Pull Request, or send an e-mail to docs@c9.io, and we'll get it in.

\\n

Recently Updated Topics

\\n

Here's a list of the last five recently updated topics:

\\n\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_hosted_mysql\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"MySQL\",\n \"contents\": \"\\n
\\n

MySQL

\\n

MySQL is the world's most widely used open source relational database management system (RDBMS) that runs as a server providing multi-user access to a number of databases.

\\n

MySQL's most common features

\\n
    \\n
  • A broad subset of ANSI SQL 99, as well as extensions
    • \\n
  • Cross-platform support
    • \\n
  • Stored procedures
    • \\n
  • Triggers
    • \\n
  • Cursors
    • \\n
  • Updatable Views
    • \\n
  • Information schema
    • \\n
  • Many more
    • \\n
\\n

Using MySQL with Cloud9

\\n

Cloud9 IDE does not support installing a MySQL database (yet). As a workaround you can choose to connect your project to a MySQL database hosted elsewhere. Xeround\\noffers hosted MySQL instances and have a free tier available for getting started.

\\n

Xeround

\\n
    \\n
  1. Register with Xeround
    2. \\n
  2. Log in to your controlpanel
    3. \\n
  3. Choose 'create new'
    4. \\n
  4. Choose a datacenter
    5. \\n
  5. Enter your Database name, Username and Password and create
    6. \\n
  6. Select your newly created instance and click the 'External DNS Hostname' link provided to log into PHPMyAdmin
    7. \\n
  7. Create and import/setup your database
    8. \\n
\\n

Cloud9

\\n
    \\n
  1. Log into your account
    2. \\n
  2. Create a new project (or use an existing one)
    3. \\n

  3. Test the connection using the following script:

    \\n
             <?php\\n\\n         $database = new mysqli('instanceNo.db.xeround.com', 'username', 'password', 'databasename', 'port');\\n\\n         if($database->connect_errno > 0){\\n             die ('Database Error' . $database->connect_error); \\n         }else{\\n             die ('Connected!');\\n         }\\n         ?>
    \\n
    4. \\n
  4. Save the file
    5. \\n
  5. Run the file
    6. \\n
\\n

Source

\\n

Courtesy of Roger Qui of Polycadamy. This guide is elaborately explained in a video tutorial

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"project_bar\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"The Project Bar\",\n \"contents\": \"\\n

The Project Bar

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n

The project bar is located towards the left of the Cloud9 IDE: \\\"The

\\n

The buttons in the project bar allow you to reveal and hide panels for the IDE. In more detail:

\\n
    \\n
  • Pressing on the Cloud9 icon collapses the panel area
    • \\n
  • Project Files shows your workspace's directory structure. You can view all your files here. Right-clicking within this panel reveals a drop-down menu with additional options, such as the ability to rename files or create new directories.
    • \\n
  • Active Files lists your files that are currently open.
    • \\n
  • Run & Debug lets you run and debug your code live, in the browser. For more information, see the section on "Running and Debugging Your Code".
    • \\n
  • Deploy allows you to deploy to a variety of services. For more information, see the section on "Deploying Your Code".
    • \\n
  • Preferences lets you change the behavior of the editor. The Preferences documentation is provided on its own page.
    • \\n
\\n

Clicking on any button expands its menu. Clicking on an expanded menu causes it to collapse, which gives you more room in the IDE to work with.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"tab_functions\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Tab Functions\",\n \"contents\": \"\\n
\\n

Tab Functions

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n

Cloud9 IDE offers advanced tab features to make working with multiple files easy. By right-clicking on any tab, you'll open up the tab context menu:

\\n

\\\"The

\\n

These feature include:

\\n
    \\n
  • Reveal in File Tree: opens the current file in the Project Files tree
    • \\n
  • Close Tab: closes the current tab
    • \\n
  • Close All Tabs: closes all the opened files
    • \\n
  • Close All But Current Tab: closes all the opened files, except the current one
    • \\n
  • Close Tabs to the Right/Left: closes all opened tabs to the right (or left) of the current one
    • \\n
  • File Revision History...: launches the revisions panel
    • \\n
\\n

To the left of the tab menu is another button that offers additional functions for tab navigation:
\\\"The

\\n

Tab Sessions

\\n
\\n\\n
\\n\\n

Tab sessions is a unique feature that is useful when dealing with projects that involve juggling between many tabs. Essentially, tab sessions lets you save the current state of the tabs. You can close your workspace, switch to a different branch, and instantly reload your previously opened files. You'll no longer need to work with opening and closing multiple files.

\\n

To use tab sessions, select Save Tab Sessions from the tab button menu. Give it a unique name. When you're ready to restore your tab sessions, just select Load Tab Sessions.

\\n

If you find that you've got too many tab sessions defined, you can always choose to delete them from the same tab menu.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"status_bar\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Status Bar\",\n \"contents\": \"\\n

Status Bar

\\n

Note:

this feature is deprecated\\n\\n
\\n

The status bar is designed to provide you with all sorts of information about your code--and additional functionality--without getting in the way of the IDE. It's quite tiny, and quite powerful, like a weight-lifting squirrel.

\\n

You can find the status bar in the lower-right corner of the editor: \\\"The. Keep in mind that the status bar is transparent, so it's able to camoflauge well with light or dark themes.

\\n

There's three pieces of crucial information available at all times: your current row, your current column, and, if you're highlighting characters, the status bar displays the number of bytes currently selected. If you're using Vim Mode, the status bar also tells you if you're in INSERT mode.

\\n

If you click on the status bar, it expands into a menu that provides a smaller set of the full IDE preferences. These options only deal with the IDE editor:

\\n
\\n \\n \\n \\n \\n \\n \\n \\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
Preference NameDescription
Show InvisiblesShows invisibles characters in the editor, like tabs and line breaks
Wraps LinesWraps lines according to the line margin defined, or your browser's window. Otherwise, lines run off the current viewport.
Code FoldingWhen enabled, allows you to show or hide "blocks" of code
Full Line SelectionWhen highlighting lines, this option will highlight all ending whitespace, until the end of the editor window
Highlight Active LinePresents a darker shade in the code editor to indicate which line you're currently on
Show Indent GuidesShows the indent guides in the editor, letting you see your code's nestings
Show GutterShows the gutter in the editor, which indicates line numbers, warnings, and errors
Highlight Selected WordIf you highlight a word, this highlights all matching words in the editor
Auto-pair Quotes, Brackets, etc.When enabled, typing ", (, or [ will actually make two characters appear. In addition, whenever you highlight a word and type one of these characters, it is surrounded by that character (e.g. words becomes "words")
Auto-hide Horizontal Scrollbarhen this is enabled, this will hide the horizontal scroll bar in the editor. Note that this has no effect in Mac OS X 10.7 (Lion) and above, since all scrollbars, by default, auto-hide.
Font SizeChanges the font size of the code in the editor
Show Print MarginShows (and defines) the number of characters possible in line, before it wraps
Soft TabsIndicates how many spaces a single tab represents
Mouse Scroll SpeedDefines the speed of the mouse scrolls
\\n
\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_mysql\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"MySQL\",\n \"contents\": \"\\n
\\n

MySQL

\\n

MySQL is the world's most widely used open source relational database management system (RDBMS) that runs as a server providing multi-user access to a number of databases.

\\n

MySQL's most common features

\\n
    \\n
  • A broad subset of ANSI SQL 99, as well as extensions
    • \\n
  • Cross-platform support
    • \\n
  • Stored procedures
    • \\n
  • Triggers
    • \\n
  • Cursors
    • \\n
  • Updatable Views
    • \\n
  • Information schema
    • \\n
  • Many more
    • \\n
\\n

Using MySQL with Cloud9

\\n

This article explains our first iteration of MySQL support in Cloud9. It makes it super easy to install, start and stop a MySQL instance right in your workspace. The nice thing is that every workspace will run a separate database so your projects will never interfere with each other. You can control MySQL with the mysql-ctl command line tool run from the terminal:

\\n
# start MySQL. Will create an empty database on first start\\n$ mysql-ctl start\\n\\n# stop MySQL\\n$ mysql-ctl stop\\n\\n# run the MySQL interactive shell\\n$ mysql-ctl cli
\\n

You can then connect to the database with following parameters:

\\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
Option\\n Value\\n Comment\\n
Hostname$IPThe same local IP as the application you run on Cloud9
Port3306The default MySQL port number
User$C9_USERYour Cloud9 user name
Password-No password since you can only access the DB from within the workspace
Databasec9The database name
\\n

Importing data into your database

\\n

To import existing data into your database run following commands:

\\n
mysql-ctl cli
\\n

You are now in the MySQL environment and can start the import:

\\n
mysql> use c9\\nmysql> source PATH_TO_SQL_FILE.sql
\\n

To verify that everything got imported run:

\\n
mysql> show tables;
\\n

Note:

MySQL socket file can be found in ~/lib/mysql/socket/mysql.sock\\n\\n
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"common_errors\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Common errors\",\n \"contents\": \"\\n
\\n

Common errors

\\n

Sometimes you run into issues when you run your project. Here you will find the most common issues and how to solve them.

\\n

Address in use or similar

\\n

The most common reason for an error thrown by your app stating that a port or address is in use is the fact that some process is already running/listening on that port/address. You need to take a look for those and kill the processes conflicting with your app:

\\n
// Find the process\\nlsof -i tcp:$PORT
\\n

If any relevant process is running you will get a list looking like this:

\\n
COMMAND PID   USER   FD   TYPE   DEVICE SIZE/OFF NODE NAME\\napache2 699 ubuntu    4u  IPv6 83213152      0t0  TCP *:http-alt (LISTEN)
\\n

You now can kill that proccess. Make sure you replace PID with the ID of the process.

\\n
// Kill the process\\nkill -9 PID
\\n

For the console wizards:

\\n
kill -9 $(lsof -i:$PORT -t)
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_mongodb\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"MongoDB\",\n \"contents\": \"\\n
\\n

MongoDB

\\n

MongoDB is a scalable, high-performance, open source NoSQL database.

\\n

MongoDB's most common features

\\n
    \\n

  • Document-Oriented Storage
    \\nJSON-style documents with dynamic schemas offer simplicity and power.

    \\n
    • \\n

  • Full Index Support
    \\nIndex on any attribute, just like you're used to.

    \\n
    • \\n

  • Querying
    \\nRich, document-based queries.

    \\n
    • \\n
\\n

In addition, MongoDB has many scalability features such as:

\\n

Replication, Auto-sharding, Map/Reduce and GridFS

\\n

Running MongoDB on a Cloud9 workspace

\\n

MongoDB is preinstalled in your workspace. To run MongoDB, run the following below (passing the correct parameters to it). Mongodb data will be stored in the folder data.

\\n
$ mkdir data\\n$ echo 'mongod --bind_ip=$IP --dbpath=data --nojournal --rest \\\"$@\\\"' > mongod\\n$ chmod a+x mongod
\\n

You can start mongodb by running the mongod script on your project root:
\\n$ ./mongod

\\n

MongoDB parameters used:

\\n

| Parameter | Description |\\n| ------------------------------ | ----------------------------------------------------------------------------------------------- |\\n| --dbpath=data | Because it defaults to /var/db which isn't accessible) |\\n| --nojournal | Because mongodb usually pre-allocates 2 GB journal file (which exceeds Cloud9 disk space quota) |\\n| --bind_ip=$IP | Because you can't bind to 0.0.0.0) |\\n| --rest | Runs on default port 28017 |

\\n

Drivers

\\n

You should use the host $IP instead of localhost as your driver connection url.
\\ne.g. in Node, it is: process.env.IP

\\n

MongoDB has drivers for all supported runtimes. Following are the most commonly used drivers:

\\n

Node.JS apps

\\n

Mongoose
\\nNode-Mongodb-Native

\\n

Shell Access

\\n

To access a shell prompt for the above MongoDB run the following.

\\n
$ mongo
\\n

Check out docs.mongodb.org for details on how to use the shell

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"creating_coffeescript_app\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Create a CoffeeScript Project\",\n \"contents\": \"\\n

Create a CoffeeScript Project

\\n

For this tutorial, we'll show you how to create and run a CoffeeScript project, entirely within the Cloud9 IDE. To run any coffeescript project, you'll need to first make sure to install the coffeescript module via the Node Package Manager (npm). We're going to walk you through how to do that with a sample project.

\\n

First, create a new project. Then, in the console, enter the following command:

\\n
git clone git://github.com/fjakobs/cloud9-coffeescript-example.git
\\n

This is a sample CoffeeScript application written by one of our developers. After cloning the project, you'll find three different files in the project tree: server.js, app.coffee, and README.md.

\\n

The README.md file contains instructions to install coffee-script using npm. We've integrated Node Package Manager into Cloud9 IDE to enable users to install Node programs. Thus, from the Cloud9 IDE command line, type the following command to install the Coffeescript module:

\\n
npm install coffee-script
\\n

Next, let's have a look at the server.js file. The first line is the require() function, which is used to load the coffee-script module that you have just installed. On the second line, we declare the CoffeeScript file that contains your application. In the last line, we specify the port the server is listening to. When projects run within Cloud9 IDE, you must retrieve the port information using process.env.PORT.

\\n

Now, let's look at what the CoffeeScript file does. It creates an HTTP server with a function that is called for each request. In the callback function, you create a response with a status code of 200 (indicating that the request was fulfilled successfully) and the message "Hello World". You use module.exports to enable the server.js file to use the code in the CoffeeScript file:

\\n
http = require \\\"http\\\"\\n\\nmodule.exports = http.createServer((req, res) ->\\n    res.writeHead 200, 'Content-Type': 'text/plain'\\n    res.end 'Hello World\\\\n'
\\n

Next, run the server.js file and open the URL indicated in the console:

\\n

\\\"Messages

\\n

The result is:

\\n

\\\"The

\\n

To stop your application, go back to the editor and click on the \\\"Icon button in the Menu Bar.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"editing_wordpress_sites\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Editing Remote WordPress Websites via FTP\",\n \"contents\": \"\\n

Editing Remote WordPress Websites via FTP

\\n
\\n\\n
\\n\\n

Did you know that you can use Cloud9 IDE to work on your WordPress website? It's true, and incredibly easy. You can't edit your posts on WordPress using Cloud9, since they are stored in a database on your server. But you can edit pretty much every other aspect of your site.

\\n

To start, you'll need to create a new FTP project. After that, enter your wp-content folder, find the theme you're using on your website, and start editing its style.

\\n

Thanks to the preview button in the menu bar, you can also witness your changes as they happen, before committing them to your server.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_postgresql\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"PostgreSQL\",\n \"contents\": \"\\n
\\n

PostgreSQL

\\n

Installing PostgreSQL on a Cloud9 workspace

\\n

PostgreSQL comes preinstalled on every Cloud9 workspace, yay.

\\n

Start the PostgreSQL service

\\n
$ sudo service postgresql start
\\n

Set the "postgres" user password

\\n
$ sudo sudo -u postgres psql                                                                                  \\npsql (9.3.4, server 9.3.5)\\nType \\\"help\\\" for help.\\n\\npostgres=# \\\\password\\nEnter new password: \\nEnter it again: \\npostgres=# \\\\q
\\n

Connect to the service

\\n
$ sudo sudo -u postgres psql
\\n

Create a PostgreSQL database

\\n

Make sure you have logged into the PostgreSQL terminal and then you can just run:

\\n
$ sudo sudo -u postgres psql                                                                                  \\npostgres=# create database \\\"groceries\\\";
\\n

List all databases

\\n
$ sudo sudo -u postgres psql                                                                                  \\npostgres=# \\\\list
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"installing_npm_modules\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Installing NPM Modules\",\n \"contents\": \"\\n

Installing NPM Modules

\\n

Since Cloud9 IDE is built on top of Node.js, we also leverage the module system NPM. In Cloud9, you can install any npm package either locally or globally. Note that due to security restrictions, modules installed globally can only be used in the project they were installed from. In other words, while you have access to any command line tools installed by the module, they are bound to the project, not your username. We run version 1.1.24 of npm.

\\n

To demonstrate the power of NPM, we'll build and run a quick express server:

\\n
    \\n
  1. Launch the command line by hitting Shift-Escape. You can also go to View > Command Line if it's not visible.
    2. \\n
  2. Type npm install express, and wait for the npm install process to complete.
    3. \\n
  3. Create a new JavaScript file, and paste the following code:
    4. \\n
\\n
var express = require('express'),\\n    app = express();\\n\\napp.use(express.logger());\\n\\napp.get('/', function(req, res){\\n    res.send('Hello World');\\n});\\n\\napp.listen(process.env.PORT);\\nconsole.log('Express server started on port %s', process.env.PORT);
\\n

To launch your express server, click on the \\\"The button in the menu bar.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"installing_python_packages\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Installing Python Packages\",\n \"contents\": \"\\n

Installing Python Packages

\\n

Cloud9 supports the installation of Python packages for applications that need to go beyond the standard library set. Every workspace has version 0.6.10 of Python's easy_install package manager. For more information on this module, see the official easy_install documentation.

\\n

Let's try installing a package. First, type the following in the console:

\\n
easy_install markdown
\\n

This installs the markdown Python package to your workspace. You won't see the package installed in the directory tree, because it's kept deep within your project's the Python libs.

\\n

Next, create a new Python script, and add these lines of code:

\\n
import markdown\\n\\nhtml = markdown.markdown(\\\"# HELLO THERE!\\\")\\n\\nprint html
\\n

After clicking run, the console will correctly print out <h1>HELLO THERE!</h1>.

\\n

You have access to all of the functionality easy_install provides you. For example, you can open up the Python REPL and type the following to see a list of your installed packages:

\\n
>>> help('modules')
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_redis\",\n \"mtime\": 1416998221000,\n \"pageTitle\": \"Redis\",\n \"contents\": \"\\n
\\n

Redis

\\n

Running

\\n

Cloud9 workspaces come with redis pre-installed.

\\n

Start the server:

\\n
sudo service redis-server start
\\n

Connect with the client:

\\n
./redis-cli
\\n

Drivers

\\n

See http://redis.io/clients for drivers.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_sqlite3\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"SQLite\",\n \"contents\": \"\\n
\\n

SQLite

\\n

SQLite is a software library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine. SQLite is the most widely deployed SQL database engine in the world. The source code for SQLite is in the public domain.

\\n

Note:

SQLite supports full text search and ACID transactions (atomic, consistent, isolated, and durable)\\nWith its simplicity and zero-configuration, SQLite is a popular choice for new applications.\\n\\n
\\n

Getting started

\\n

You can open the terminal and create a database in a file db_test.db as follows:

\\n

\\\"Screenshot

\\n

Try yourself

\\n
$ sqlite3 db_test.db\\nSQLite version 3.6.20\\nEnter \\\".help\\\" for instructions\\nEnter SQL statements terminated with a \\\";\\\"\\nsqlite> create table tbl1(one varchar(10), two smallint);\\nsqlite> insert into tbl1 values('hello!',10);\\nsqlite> insert into tbl1 values('goodbye', 20);\\nsqlite> select * from tbl1;\\nhello!|10\\ngoodbye|20\\nsqlite> CREATE TABLE tbl2 (\\n   ...>   f1 varchar(30) primary key,\\n   ...>   f2 text,\\n   ...>   f3 real\\n   ...> );\\nsqlite> .exit
\\n

To get to know sqlite commands, use the command: .help.

\\n

To exit sqlite, use the command: .exit.

\\n

Drivers

\\n

SQLite has drivers for all supported runtimes.

\\n

Following are the most commonly used drivers:

\\n

Node.JS apps

\\n

node-sqlite

\\n

Rails apps

\\n

In your Gemfile, include the line:

\\n
gem 'sqlite3'
\\n

and in configs/database.yml, make sure you use:

\\n
adapter: sqlite3\\ndatabase: db/development.db
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"running_a_rails_app\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Running a Rails App\",\n \"contents\": \"\\n
\\n

Running a Rails App

\\n

Cloud9 IDE also supports the ability to run a Rails application. The rails command is only available on the terminal.

\\n

To run a rails application:

\\n
    \\n
  1. Open the terminal and type gem install rails
    2. \\n
  2. When done, type rails new example -d mysql
    3. \\n
  3. Edit your database configuration in configs/database.yml
    4. \\n
  4. Type rails s -b $IP -p $PORT
    5. \\n
\\n

That's it! Your rails app will now be running.

\\n

Note:

http://<workspacename>-c9-<username>.c9.io should be running your application.\\n\\n
\\n

Do not try to access the project through the IP address and port number rails returns to you--it won't work!

\\n

Use MySQL in your rails app

\\n
    \\n

  1. Setup MySQl - note your DB connect parameters

    \\n
    2. \\n

  2. edit configs/database.yml

    \\n
    3. \\n
\\n
development:\\n  adapter: mysql2\\n  encoding: utf8\\n  database: c9\\n  username: <%=ENV['C9_USER']%>\\n  host: <%=ENV['IP']%>
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"installing_ruby_gems\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Installing Ruby Gems\",\n \"contents\": \"\\n

Installing Ruby Gems

\\n

Cloud9 supports the installation of Ruby gems in your workspace using the RubyGems package manager. The current installed RubyGems version is 1.3.7. For more information on the gem command, see the official RubyGems documentation.

\\n

Let's try installing a gem. First, type the following in the console:

\\n
gem install progressbar
\\n

This installs the progressbar Ruby gem to your workspace. You won't see the gem installed in the directory tree, because it's kept deep within your project's the Ruby libs.

\\n

Next, create a new Ruby script, and add these lines of code:

\\n
require 'progressbar'\\n\\nbar = ProgressBar.new(\\\"Example progress\\\", 50)\\ntotal = 0\\nuntil total >= 100\\n  sleep(rand(2)/2.0)\\n  increment = (rand(6) + 3)\\n  bar.inc(increment)\\n  total += increment\\nend
\\n

After clicking run, the console will start printing out an ASCII progressbar.

\\n

You have access to all of the functionality gem provides you. For example, you can open up the console and type gem query to see a list of your installed gems.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"running_wordpress_on_cloud9\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Running WordPress on Cloud9\",\n \"contents\": \"\\n
\\n

Running WordPress on Cloud9

\\n

WordPress is web software you can use to create websites or blogs.\\nYou can develop and host WordPress websites entirely on Cloud9 IDE

\\n

Creating a wordpress workspace

\\n

Create a WordPress workspace from the WordPress template on your Cloud9 dashboard

\\n

Note:

We will download, extract and configure WordPress for you.\\n\\n
\\n

In order to run WordPress, you need a database to host your posts, articles, etc.

\\n

You can use MySQL with our utility script mysql-ctl as explained in MySQL Setup

\\n

Running the website

\\n

To start MySQL server and create the required database, type in the terminal:

\\n
mysql-ctl start
\\n

Open index.php in your workspace root and click the Run button

\\n

You can check the generated config for you In wp-config.php (you don't need to change anything there)

\\n
define('DB_NAME', 'c9');\\ndefine('DB_USER', getenv('C9_USER'));\\ndefine('DB_PASSWORD', '');\\ndefine('DB_HOST', getenv('IP'));\\ndefine('WP_SITEURL', 'http://' . getenv('C9_PROJECT') . '.' . getenv('C9_USER') . '.c9.io');
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"running_and_debugging_code\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Running and Debugging Your Code\",\n \"contents\": \"\\n
\\n

Running and Debugging Your Code

\\n

Cloud9 IDE provides several ways to run and debug your code. We'll explore each of them in this section of the documentation.

\\n

Note:

Currently, only Javascript/Node.js applications can make use of the debugger. You can also execute Javascript/Node.js, Python, Ruby, and Apache+PHP applications.\\n\\n
\\n

The following information applies to all of the above programming languages.

\\n

Running Code

\\n

Running your code in Cloud9 is really easy. First, open the file you want to run. Usually, this file is going to be the main entry point to your app; for example, if you're creating a server, you'd want to run the file that actually instantiates that server.

\\n

There are two ways to run your code: either through the Run Panel, or through the run button in the menu bar.

\\n

Using the Run Panel

\\n

Next, click on the Run button in the project bar. You'll notice immediately that your active file is already available to run. Just double-click on the file, and you'll launch your app.

\\n

When you're ready to stop your app, click on the \\\"Icon button in the menu bar at any time.

\\n

At the bottom of the run panel, you'll notice a few more options you can set. Filling these textboxes out creates a run scenario, which is like setting up some configurations for the way your code runs. These options are:

\\n
    \\n
  • Name the name of your run scenario
    • \\n
  • File Path: the location of your running file in your project
    • \\n
  • Runtime: defines how you want your code to be run. Typically, you'd set different runtime versions here.
    • \\n
  • Cmd Line Args: allows you to provide any additional command line arguments you want to pass to your app
    • \\n
\\n

Of course, you can also save your run scenarios; just click on the add button at the top of the panel. When you're ready to run a scenario, click on its name in the Run panel list. To remove a run scenario, click on its name in the run panel list, and then click on the remove button.

\\n

Using the Run Button

\\n

The run button in the menu bar acts as a sort of short cut to the Run panel. When clicked, the button automatically runs the currently active file. If you have a list of run scenarios already defined, the run button also presents a list of those:

\\n

\\\"Run

\\n

Run in debug mode indicates that you want to run the current code through the debugger. Auto show & hide debug tools will reveal (or collapse) the debugging tools panel described below. You can also work with this presentation by going to View > Panels, and configuring the debugger there.

\\n

Console Output

\\n

Every time you run a project, the console expands to reveal output from your program. If you're launching a server, Cloud9 provides you with a URL to access the project. Otherwise, any statements sent by your application's print statements (like console.log() for Javascript, print for Python, or puts for Ruby) are also shown here. For example:
\\\"Console

\\n

Debugging Your Code

\\n

Setting up a project to debug is done in very much the same way as running your code. The only difference is that you must click on the run settings icon in the Run panel \\\"Run and select Run in debug mode. Similarly, you can select Run in debug mode from the run button.

\\n

Initially, the only difference this will make is the expansion of the debugging toolbar to the right of the editor:
\\\"The

\\n

This toolbar, however, grants you the following capabilities:

\\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
Toolbar IconDebugging FunctionDescription
\\\"DebuggingDebugging NavigationThis is a set of tools you can use to move around your code while debugging. You can step into, over, and out of your code, or simply press play to run the process until the next breakpoint.
\\\"IconCallstackThis is a structured list of information about the sequences of your code--basically, which functions are calling what, and where you are in the current process. It also stores local variables and function arguments, if present. You can use this feature to check how your code is running:
\\\"Callstack
\\\"IconInteractive ModeLets you evaluate a piece of code, such as expressions or the values and properties of variables. The text field allows you to type any code you want, in case you discover a way to fix you problem:\\n\\\"Interactive
\\\"IconVariable InspectionThis shows all the related variables (including functions) that are present in the current context:\\n\\\"Variable
\\\"IconBreakpoint ListAt any point during your coding or debugging session, you can click on the gutter to apply a breakpoint: \\\"Breakpoint. When debugging your code, the process pauses at your established breakpoints, so that you can inspect closely what's going on in a certain part of the code. You can click on the breakpoint list to view all the breakpoints in your workspace. If you click on the checkbox, you can enable or disable a breakpoint as well. You can also click on a breakpoint in the gutter to disable or enable it.
\\n

While debugging, you also have the power of the live inspector. While hovering over a piece of code in the editor, you'll instantly get some floating text that describes the values of that variable, similar to Variable Inspection.
\\\"Live

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"writing_a_python_app\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Writing a Python App\",\n \"contents\": \"\\n

Writing a Python App

\\n

While using Cloud9 IDE, you have access to the Python runtime. Accessing the command is no different than the way you'd use Python on your computer; just open the command line and type python. Currently, we run version 2.6.6.

\\n

To run a Python program that you've created, you can either:

\\n
    \\n
  • Open the command line and type python, followed by the name of your program; for example python hello_world.py
    • \\n
  • Create a new run scenario, so that you can do things like pass in command line arguments
    • \\n
\\n

As a quick demonstration, open a new file, and paste this Python code into it:

\\n
#!/usr/bin/python\\n\\nprint \\\"Hello World!\\\";
\\n

When you hit the \\\"The button in the menu bar, the console will print out Hello World!.

\\n

Note:

Currently, you can't debug Python applications, but we are working on adding this feature.
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"writing_a_go_app\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Writing a Go App\",\n \"contents\": \"\\n
\\n

Writing a Go App

\\n

Cloud9 IDE doesn't provide out-of-the-box support for the Go language, but with \\na few quick steps you can set up Cloud9 to build and run apps in Go!

\\n

Create a new workspace

\\n

First, create a new Custom workspace and call it whatever you want:

\\n

\\\"Create

\\n

After your new workspace is created, click the "start editing" button. At the \\nbottom of your workspace you will see the Terminal. If you prefer to have it\\nfullscreen, you can launch a terminal tab by pressing Alt-T, or from the menu: \\nView > Terminals > New Terminal.

\\n

From the terminal you can install & setup everything on the underlying virtual \\nenvironment that every workspace is provided with.

\\n

Download Go

\\n

When you first enter your Terminal, you will be in your workspace root folder, \\nwhich is a number such as ~/562166. Make a note of this directory name, as \\nyou'll need it later.

\\n

Let's use your home directory to download the Go distribution; to get there, \\nsimply enter the following in the Terminal:

\\n
cd ..
\\n

To download the Go distribution enter the following:

\\n
wget https://go.googlecode.com/files/go1.1.1.linux-amd64.tar.gz
\\n

Note:

at the time of writing the latest version was 1.1.1, but you might want to \\nuse a new version if it has become available. \\n\\n
\\n

After the download is complete, extract the archive:

\\n
tar -xzf go1.1.1.linux-amd64.tar.gz
\\n

Once the extraction is done, you will notice a new go directory in your home \\ndirectory. Feel free to delete the archive file you downloaded.

\\n

Set up your environment

\\n

The last step is to configure the environment so it can see the Go distribution \\nas well as our workspace Go files. To do this, edit your bash configuration \\nin the Terminal using vim (or emacs, nano, any simple editor will do):

\\n
vim ~/.bashrc
\\n

Add the following lines to your .bashrc file:

\\n
# setup go configuration \\nexport GOROOT=$HOME/go \\nexport PATH=$PATH:$GOROOT/bin \\n\\n# setup workspace t\\nexport GOPATH=$HOME/562166 \\nexport PATH=$PATH:$GOPATH/bin
\\n

Update the GOPATH line above to use the workspace directory you noted earlier \\n(so don't use $HOME/562166).

\\n

After you save your .bashrc file, load the new settings:

\\n
source ~/.bashrc
\\n

That's it! You should be good to Go (pun intended).

\\n

Note:

Thanks to Scotty Moon for writing an article about Go on Cloud9 IDE\\nand letting us use it for documentation!
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"terminal_monitor\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"The Terminal Monitor\",\n \"contents\": \"\\n

The Terminal Monitor

\\n

Many times your app returns errors which are hard to understand and even harder to resolve. This is where the Terminal Monitor comes in.\\nThe following video gives a quick overview of the features and how the Terminal Monitor helps you write better apps.

\\n\\n\\n

If you would like to propose additions or help which Terminal Monitor should provide, please send a message to support@c9.io

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"writing_a_ruby_app\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Writing a Ruby App\",\n \"contents\": \"\\n
\\n

Writing a Ruby App

\\n

While using Cloud9 IDE, you have access to the Ruby runtime. Accessing the command is no different than the way you'd use Ruby on your computer; just open the command line and type ruby. Currently, the default version is 1.9.3.

\\n

To run a Ruby program that you've created, you can either:

\\n
    \\n
  • Open the command line and type ruby, followed by the name of your program; for example ruby hello_world.rb
    • \\n
  • Create a new run scenario, so that you can do things like pass in command line arguments
    • \\n
\\n

As a quick demonstration, open a new file, and paste this Ruby code into it:

\\n
#!/usr/bin/ruby\\n\\nputs 'Hello world'
\\n

When you hit the \\\"The button in the menu bar, the console will print out Hello world.

\\n

Note:

Currently, you can't debug Ruby applications, but we are working on adding this feature.\\n\\n
\\n

RVM Support

\\n

We have rudimentary support for rvm, that allows you only to switch between versions 1.8.7 and 1.9.3. We don't support rvm per-project or global gemsets.

\\n

To use rvm, open the terminal and type:

\\n
# to switch to version 1.8.7\\nrvm use 1.8\\nrvm use 1.8.7 \\n\\n# to switch to version 1.9.3\\nrvm use 1.9\\nrvm use 1.9.3
\\n

However, if you like, you can install the "real" rvm by executing the following command in the terminal:

\\n
curl -L https://get.rvm.io | bash -s stable
\\n

To grab the latest rvm AND the latest Ruby version, type:

\\n
curl -L https://get.rvm.io | bash -s stable --ruby
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"creating_new_workspace\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Creating a New Workspace\",\n \"contents\": \"\\n
\\n

Creating a New Workspace

\\n

Cloud9 supports three types of workspaces:

\\n
    \\n
  1. Hosted
    2. \\n
  2. FTP
    3. \\n
  3. SSH
    4. \\n
\\n

In this article, we'll walk you through the creation of a new workspace and describe the choices you encounter.

\\n

The first step for creating a new workspace is click the "CREATE NEW WORKSPACE" button in your Dashboard:

\\n

\\\"New

\\n

At this point, you'll encounter two choices: Create a new workspace and Clone from URL. Here's what they mean:

\\n
    \\n
  • Create a New Workspace allows you to create any of the previously mentioned types of workspaces (hosted, FTP, or SSH).
    • \\n
  • Clone from URL allows you to instantly create a workspace from a repository, like GitHub or Bitbucket, using its URL. We'll explain more about this in the section below.
    • \\n
\\n

Create a New Workspace

\\n

After clicking on Create a new workspace, you're taken to the screen below:

\\n

\\\"Options

\\n

First, let's enter a workspace name.\\nDepending on whether you have a Free of Premium account, you can choose to make it either Public (open to anyone with the URL), or Private (only accessible to you and people you share it with).

\\n

After this, choose the type of workspace you want to create:

\\n
    \\n
  • Hosted: This is a regular Cloud9 workspace, powered by a full Ubuntu environment. You even have sudo powers! This is the best choice for most people, and we've included some more info about it below.
    • \\n
  • FTP allows you to upload your files directly to an FTP server that you have access to
    • \\n
  • SSH, also called the "bring your own server" feature, lets you log into a server you own and run Cloud9 from there
    • \\n
\\n

Make a choice for the type of workspace and press Create. That's it! You can now see your new workspace in the dashboard:

\\n

\\\"New

\\n

Now, just click Start Editing to get started!

\\n

Hosted workspaces

\\n

Choose this workspace type to start from scratch with a 'Custom' workspace, or simply pick a pre-configured environment like Node.js, WordPress, or Python/Django, and immediately start developing your app.\\nThis way you don't need to spend valuable development time on system setup and maintenance, as we maintain it, and you control it.

\\n

\\\"Options

\\n

As it's powered by a full Linux Ubuntu environment, hosted workspaces allow you to install any package (sudo apt-get install package), run git commands from the console to push your changes to a GitHub repo or a Bitbucket git repo, etcetera.

\\n

Cloning from a URL

\\n

The second option for creating a new workspace is to clone one from URL. The URL would be, for example, the URL of a GitHub workspace.

\\n

In fact, let's clone a workspace. When you click on Clone from URL, you're taken to this screen:

\\n

\\\"Options

\\n

Paste the following GitHub URL in the textbox labeled Source URL: https://github.com/mattpardee/geekdots

\\n

If you have a premium account, you can choose who has access to your workspace. For regular users, the new workspace will be public.

\\n

Now, check out the workspace. It will be created under My Workspaces. You can now start editing it!

\\n

Deleting a Workspace

\\n

Now that you know how to create a workspace, you should also learn how to delete one. Look at the far right side of your dashboard:

\\n

\\\"Delete

\\n

Clicking on the Delete button prompts the IDE to ask for confirmation:
\\\"Confirmation

\\n

This is your last chance to change your mind. Once you have typed delete in the textbox and pressed the red button, your workspace will be gone forever from Cloud9. If you are sure you want to delete your workspace, go ahead and press the red button. Of course, if your workspace is hosted elsewhere, like on another git or FTP server, it still exists in those repositories.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"ftp_workspaces\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Setting up an FTP project\",\n \"contents\": \"\\n

Setting up an FTP project

\\n
\\n\\n
\\n\\n

In this article, we'll show you how to set up an FTP project.

\\n

Note:

Currently, Cloud9 IDE only supports passive FTP. Active FTP, SFTP and FTPS are not yet supported. For SSH connections, consider creating an SSH workspace.\\n\\n
\\n

To create an FTP project, go to the Dashboard and click on the \\\"Project next to MY PROJECTS. Choose the option to Create a new project (see "Creating a New Project" if you need to review the steps to create a new project):
\\\"New

\\n

In the pop-up window that appears, select FTP for the project type:

\\n

\\\"FTP

\\n

Let's review the options available for your FTP project:

\\n
    \\n
  • Hostname: the domain name or IP address of the machine running your FTP server.
    • \\n
  • Username: your username for the FTP server.
    • \\n
  • Password: your password for the FTP server.
    • \\n
  • Initial path: this is an optional parameter. You can set it as an absolute (starts with /) path. Otherwise, it'll be set to a relative path, and Cloud9 assumes that you want to start from the folder your FTP server leaves you after login (home or default folder).
    • \\n
\\n

Warning:

Be careful not to put an initial path that leaves you in a location where you don't have write privileges as that could cause problems.\\n\\n
\\n

Fill in your FTP details and click the Login Test to verify that the settings are correct. If the test succeeds, go ahead and click Create to create your FTP project. You'll then see your project in the Dashboard under My Projects:

\\n

\\\"New

\\n

When your new FTP project is selected, you will see three buttons: Start Editing, FTP settings, and Delete (on the far right). FTP settings gives you access to the settings you just filled in, as well as the login test. This is useful to use in case your login credentials have changed.

\\n

To get started with your FTP project, click on the Start Editing button. You'll be taken to the editor. Under Project Files, you should see the files from the FTP server in the directory you selected (either your home/default folder or the location indicated by the Initial Path, if you set it). The editor for FTP projects works the same as in other projects: you can create and edit your files in the usual way. The main difference is the FTP log at the bottom of the page (where the console is usually located for other non-FTP projects).

\\n

The FTP log displays output related to the interaction with the FTP server. The screenshot below, for example, shows what happens when we create a new file called TestFile.txt. The file is created in the FTP server and when I write to it, the contents are transferred.

\\n

\\\"Demonstrating

\\n

Note:

In an FTP project, all files are stored on your FTP server; Cloud9 only stores the FTP settings. Please keep this in mind. Cloud9 IDE does not keep any copies of your files, so make sure you back them up properly. Any changes you make to these files in Cloud9 are automatically reflected on the live web server.
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"writing_nodejs_hello_world\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Writing and Running a Node.js Program\",\n \"contents\": \"\\n
\\n

Writing and Running a Node.js Program

\\n

Cloud9 IDE was built on top of the Node.js platform, and as such, you have full access to the node runtime. Currently, we support running both version v0.6.x and v0.8.x.

\\n

In this section, we'll walk you through the creation of a simple Hello World program. To get started, you'll first need to create a (GitHub or Mercurial) project. If you need a refresher on how to do this, please refer to Creating a New Workspace.

\\n

A Simple Node.js HTTP Server

\\n

Once you're in Cloud9, create a new file called server.js. Type the following code in the file:

\\n
var http = require('http');\\nhttp.createServer(function (req, res) {\\n    res.writeHead(200, {'Content-Type': 'text/plain'});\\n    res.end('Hello World\\\\n');\\n}).listen(process.env.PORT, process.env.IP);
\\n

This is a Node.js HTTP server. It returns a simple "Hello World" page every time you access the page. In short, you are creating an HTTP server with a callback function that is called for each request.

\\n

In the callback function, you create a response with a status code of 200 (indicating that the request was fulfilled successfully) and the message "Hello World". Finally, you specify which port and IP address the server runs on. When Cloud9 IDE runs servers, you set and retrieve the IP address and port number with the process.env.IP and process.env.PORT variables.

\\n

When you hit the \\\"The button in the menu bar, the console will print out the following message:
\\\"Console

\\n

To see your application in action, click on the link created for your project. You should see your "Hello World" application open up in a new browser tab:
\\\"Node.js.

\\n

NVM Support

\\n

We have rudimentary support for nvm, that allows you only to switch between Node.js versions 0.6.21 and 0.8.x.

\\n

To use nvm, open the terminal and type:

\\n
# to switch to version 0.6.21\\nnvm use v0.67 \\n\\n# to switch to the latest 0.8.x\\nnvm use v0.8
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"writing_a_php_app\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Writing a PHP App\",\n \"contents\": \"\\n
\\n

Writing a PHP App

\\n

With Cloud9 IDE, you can run your PHP pages, without relying on a third-party system like Apache hosting. We run PHP version 5.3.3.

\\n

You can choose to run PHP scripts via the command line, by typing php, followed by the name of your PHP file. However, this is not a very common use case. Most likely, you'll be running your own server and hosting PHP files.

\\n

Here's a simple demonstration. First, create a PHP file called hello_world.php, and paste this code into it:

\\n
<html>\\n  <head>\\n   <title>PHP Test</title>\\n  </head>\\n  <body>\\n   <?php echo '<p>Hello World</p>'; ?> \\n  </body>\\n</html>
\\n

Next, open the Run & Debug panel, at the left of the IDE. From the Runtime dropdown, select Apache+PHP. Then, click on the \\\"The button in the top menu bar.

\\n

The console should now spit out a message about how your Apache server is running, something similar to this:

\\n
Running Apache Process\\nTip: you can access long running processes, like a server, at 'http://php_hello.gjtorikian.c9.io'.
\\n

Clicking on that link gets you to your PHP page. For a more in-depth workflow, see the article on running WordPress entirely on Cloud9.

\\n

Modifying php.ini

\\n

You can configure your PHP installation by editing the php.ini located in the /home/ubuntu/workspace directory. Please note: in some cases php.ini is located somewhere else. Just create a simple PHP file running phpinfo() to find out where to look for php.ini.

\\n

Make sure to restart Apache after you have applied your changes

\\n
apachectl restart
\\n

Note:

Currently, you can't debug PHP applications yet, but we are working on adding this feature.\\n
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_bitbucket_workspace\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Setting Up a Bitbucket Workspace\",\n \"contents\": \"\\n
\\n

Setting Up a Bitbucket Workspace

\\n

Bitbucket is a code-hosting services that offers both git and mercurial support. Projects can be listed as private or public, absolutely free. For more information on Bitbucket, visit https://bitbucket.org.

\\n

We have integrated Bitbucket into the IDE to enable you to easily work on your public and private repositories. The following article explains how you can activate your Bitbucket account in Cloud9 IDE.

\\n

Bitbucket Activation

\\n

You can manage your add-on services from your user profile that you can find in the dashboard. When you have just signed in, click Your Account on the top of the left-side panel. Here, you can change the settings of your account. At the bottom, you'll see a list of add-on services that are integrated into Cloud9 IDE. Click activate on the Bitbucket button:

\\n

\\\"Add-on

\\n

A new window will pop-up on your screen. This window asks you to give authorization permission for the Cloud9 IDE application to interact in various ways with Bitbucket:

\\n

\\\"Bitbucket

\\n

To finalize the activation, click on Allow. Next, you're redirected to your account page, where you'll notice that your Bitbucket account is activated. You can deactivate Bitbucket by simply clicking deactivate, which may be useful when you want to link your Bitbucket account to another Cloud9 account.

\\n

Now that you have activated Bitbucket, you can start to create and manage your projects!

\\n

Managing Projects

\\n

There are several ways to manage Bitbucket projects in Cloud9 IDE:

\\n
    \\n
  • By creating a new git or mercurial project and pushing it to Bitbucket
    • \\n
  • By cloning a Bitbucket project from a URL
    • \\n
  • By bringing in a Bitbucket project manually
    • \\n
\\n

Creating a New Git Project

\\n

New projects are created from the dashboard. In the left-side panel, click on the \\\"Project to add a new project:

\\n

\\\"New

\\n

A new window will pop-up in which you can change your settings to your preferences:

\\n
    \\n
  • Fill in your preferred project name in the text field
    • \\n
  • Choose who will have access to the project (a feature for Premium customers)
    • \\n
  • Select your project type (git, mercurial, or FTP)
    • \\n
  • Choose a development server (a feature for Premium customers)
    • \\n
\\n

\\\"New

\\n

After you click CREATE, the project is listed in your dashboard. Select the project to see its Project Profile, where you can start editing: \\\"Start

\\n

There are a couple of things you should do first, before you can use all of git's power. First, you'll want to add a remote to the project. From the Cloud9 IDE command line, you can execute the following commands:

\\n
git remote add [remote name] [remote url]
\\n

remote url is the location of the project on Bitbucket; for example 'origin git@bitbucket.org:username/repository_name.git'. You'll have to create a Bitbucket project first in order to generate this URL. Adding a remote URL lets you freely push and pull your project.

\\n

Next, create a few new files inside your project. By default, you should already have a README.md. You can add these files to git with the following command:

\\n
git add [file1, file2, file3, ...]
\\n

Finally, create a commit that you can push to your remote:

\\n
git commit -m 'added new files'
\\n

Don't forget to push this commit out to Bitbucket:

\\n
git push [remote name] master
\\n

Ta-da! Your project is developed on Cloud9, and stored in Bitbucket.

\\n

Cloning Projects from a URL

\\n

You can also create a project in Cloud9 IDE by cloning it from a URL. Once again, click on the \\\"Project, and select Clone from URL. A new window pops up, asking you:

\\n
    \\n
  • to enter a Source URL
    • \\n
  • to choose who will have access to the project (Premium feature)
    • \\n
  • to choose a development server (Premium feature)
    • \\n
\\n

\\\"Clone

\\n

You can find an examples of a Bitbucket URL on any of their repo description pages:

\\n

\\\"Bitbucket

\\n

Paste the URL in the source field and click CHECKOUT. In the left-side panel, you'll see the project and its status turn into "Cloning in Progress". When this process is completed you can open the project and start editing it, just like any other project.

\\n

Clone Projects Already On Bitbucket

\\n

When you provide Cloud9 IDE with your Bitbucket credentials, it provides a list of projects you haven't yet imported into the editor:

\\n

\\\"Bitbucket

\\n

From this list, clicking on a project and selecting CLONE TO EDIT brings the repo into the IDE, just as if you cloned it from a URL.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"run_your_own_workspace\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Running Your Own SSH Workspace\",\n \"contents\": \"\\n
\\n

Running Your Own SSH Workspace

\\n

You have access to an incredibly powerful feature of Cloud9 that we like to call "running your own workspace."

\\n

If you own a server that you can SSH into, you can log into that machine with Cloud9 and work on your projects remotely. To put this into perspective, you could have an entire toolchain set up on this machine--say, make with gcc, or ant with Java--edit the files with Cloud9 IDE, and build your toolchain via the IDE's terminal. Here's a video demonstrating how you could instantly compile a C program using an SSH workspace and Cloud9:

\\n
\\n\\n
\\n\\n

Connection Prerequisites

\\n

In order to connect Cloud9 with a server you own, you'll need two things:

\\n
    \\n
  1. Node.js installed on the server. This version must be between Node.js version 0.6.16 and the latest 0.8.x.
    2. \\n
  2. Your public SSH key must be saved on the server at ~/.ssh/authorized_keys. This is to ensure the utmost security between your client computer and the machine you're attempting to access. Cloud9 provides you with your SSH key in the workspace dialog; it is up to you to save it to the appropriate path. For more information on SSH keys, see this article.
    3. \\n
\\n

Tip:

If you're behind a firewall, you can identify which IP address and port Cloud9 is running on by typing echo $OPENSHIFT_INTERNAL_IP and echo $OPENSHIFT_INTERNAL_PORT into the console. You can use this information to open any blocked connections.\\n\\n
\\n

Creating an SSH Workspace

\\n

Once you've got those requirements set up, here's how you can create an SSH workspace of your own:

\\n

In the Projects tab on the Dashboard, click on the \\\"Project next to MY PROJECTS and choose the option to Create a new project (see "Creating a New Project" if you need to review the steps to create a new project):
\\\"New

\\n

In the pop-up window that appears, select SSH for the project type:
\\\"SSH

\\n

You don't need to fill out every option provided by the dialog. Let's review what they are:

\\n
    \\n
  • Hostname: the domain name or IP address of the machine running your SSH server.
    • \\n
  • Username: your username for the SSH server.
    • \\n
  • Node.js Binary Path: the locaton of your Node.js binary. If you're not sure where it is, you can always let Cloud9 guess it for you. Otherwise, on your server, type which node, to see the full path
    • \\n
  • Initial path: this is an optional parameter. You can set it as an absolute (starts with /) path. Otherwise, it'll be set to a relative path, and Cloud9 assumes that you want to start from the folder your SSH server leaves you after login (usually the home or default folder).
    • \\n
  • Port: this is an optional parameter. Cloud9 will automatically try to connect on port 22
    • \\n
\\n

Warning:

Be careful not to put an initial path that leaves you in a location where you don't have write privileges, as that could cause problems!\\n\\n
\\n

Fill in your SSH details and click the Login Test to verify that the settings are correct. If the test succeeds, go ahead and click Create to create your SSH connection. You'll then see your project in the Dashboard under My Projects:\\n\\\"New

\\n

When your new SSH is selected, you will see three buttons: Start Editing, SSH settings, and Delete (on the far right). SSH settings gives you access to the settings you just filled in, as well as the login test. This is useful to use in case your login credentials have changed.

\\n

Warning:

Make sure that you copied your SSH key correctly! Trailing spaces are significant, so make sure your text editor on your server is not modifying the key that Cloud9 is providing you with.\\n\\n
\\n

To get started with your SSH project, click on the Start Editing button. You'll instantly be taken to the editor, and have full access to your server's resources. As you can see in the video above, this means you can do exciting things like compiling C programs.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"ssh_workspaces\",\n \"mtime\": 1416998221000,\n \"pageTitle\": \"SSH Workspaces\",\n \"contents\": \"\\n
\\n

SSH Workspaces

\\n

To connect Cloud9 to a server via SSH, we first need to install a few dependencies on your system. \\nThis is done by an open-source installer which you can find here.

\\n

Usually the installation should succeed without any issues, but on some systems you will need to install a few dependencies manually. See below for common dependency issues you might run into.

\\n

Installing Python 2.7 on CentOS

\\n
curl -O https://www.python.org/ftp/python/2.7.6/Python-2.7.6.tar.xz\\ntar xf Python-2.7.6.tar.xz\\ncd Python-2.7.6\\n./configure --prefix=/usr/local\\nmake && make altinstall
\\n

Common errors

\\n

no configure: error: "curses not found"

\\n

To get around this issue make sure glibc-static is installed on the machine.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_github_workspace\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Setting Up a GitHub Workspace\",\n \"contents\": \"\\n
\\n

Setting Up a GitHub Workspace

\\n

GitHub is a code hosting service which offers you a lot of features to manage your public and private git repositories. For more information about GitHub and how to use it, visit https://github.com.

\\n

We have integrated GitHub into the IDE to enable you to easily work on your public and private Git repositories. The following article explains how you can activate your GitHub account in Cloud9 IDE.

\\n

GitHub Activation

\\n

You can manage your add-on services from your user profile that you can find in the dashboard. When you have just signed in, click Your Account on the top of the left-side panel. Here, you can change the settings of your account. At the bottom, you'll see a list of add-on services that are integrated into Cloud9 IDE. Click activate on the GitHub button:

\\n

\\\"Add-on

\\n

A new window will pop-up on your screen. This window asks you to give authorization permission for the Cloud9 IDE application to interact in various ways with GitHub:

\\n

\\\"GitHub

\\n

To finalize the activation, click on Allow. Next, you're redirected to your account page, where you'll notice that your GitHub account is activated. You can deactivate GitHub by simply clicking deactivate, which may be useful when you want to link your GitHub account to another Cloud9 account.

\\n

Now that you have activated GitHub, you can start to create and manage git projects!

\\n

Managing Git Projects

\\n

There are several ways to manage GitHub projects in Cloud9 IDE:

\\n
    \\n
  • By creating a new git project and pushing it to GitHub
    • \\n
  • By cloning a GitHub project from a URL
    • \\n
  • By bringing in a GitHub project manually
    • \\n
\\n

Creating a New Git Project

\\n

New projects are created from the dashboard. In the left-side panel, click on the \\\"Project to add a new project:

\\n

\\\"New

\\n

A new window will pop-up in which you can change your settings to your preferences:

\\n
    \\n
  • Fill in your preferred project name in the text field
    • \\n
  • Choose who will have access to the project (a feature for Premium customers)
    • \\n
  • Select your project type (git, mercurial, or FTP)
    • \\n
  • Choose a development server (a feature for Premium customers)\\n{: #setupOptions}
    • \\n
\\n

\\\"New

\\n

Select git as your project type. After you click CREATE, the project is listed in your dashboard. Select the project to see its Project Profile, where you can start editing: \\\"Start

\\n

There are a couple of things you should do first, before you can use all of git's power. First, you'll want to add a remote to the project. From the Cloud9 IDE command line, you can execute the following commands:

\\n
git remote add [remote name] [remote url]
\\n

remote url is the location of the project on GitHub; for example 'git@github.com:/ajaxorg/node_chat'. You'll have to create a GitHub project first in order to generate this URL. Adding a remote URL lets you freely push and pull your project.

\\n

Next, create a few new files inside your project. By default, you should already have a README.md. You can add these files to git with the following command:

\\n
git add [file1, file2, file3, ...]
\\n

Finally, create a commit that you can push to your remote:

\\n
git commit -m 'added new files'
\\n

Don't forget to push this commit out to GitHub:

\\n
git push [remote name] master
\\n

Ta-da! Your project is developed on Cloud9, and stored in GitHub.

\\n

Cloning Projects from a URL

\\n

You can also create a project in Cloud9 IDE by cloning it from a URL. Once again, click on the \\\"Project, and select Clone from URL. A new window pops up, asking you:

\\n
    \\n
  • to enter a Source URL
    • \\n
  • to choose who will have access to the project (Premium feature)
    • \\n
  • to choose a development server (Premium feature)
    {: #cloningOptions}
    • \\n
\\n

\\\"Clone

\\n

You can find an examples of a GitHub URL on any of their repo description pages:

\\n

\\\"GitHub

\\n

Paste the URL in the source field and click CHECKOUT. In the left-side panel, you'll see the project and its status turn into "Cloning in Progress". When this process is completed you can open the project and start editing it, just like any other project.

\\n

Clone Projects Already On GitHub

\\n

When you provide Cloud9 IDE with your GitHub credentials, it provides a list of projects you haven't yet imported into the editor:

\\n

\\\"GitHub

\\n

From this list, clicking on a project and selecting CLONE TO EDIT brings the repo into the IDE, just as if you cloned it from a URL.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_gitlab_workspace\",\n \"mtime\": 1412172002000,\n \"pageTitle\": \"Setting Up a GitLab workspace\",\n \"contents\": \"\\n

Setting Up a GitLab workspace

\\n

GitLab is open source Git management software used by more than 25.000 \\norganizations, see http://gitlab.org/.

\\n

GitLab.com offers services for on-premise GitLab installations \\nand free private git repositoring on GitLab Cloud \\nwith unlimited repo's and collaborators.

\\n

To use your on-premise GitLab installation or GitLab Cloud please see \\nthe instructions for cloning from a url.

\\n\\n
\\n
\\n \"\n }\n ],\n \"toc\": \"\\n \\n \",\n \"baseUrl\": \"https://docs.c9.io\",\n \"title\": \"Cloud9 User Documentation\"\n}" + "contents": "{\n \"files\": [\n {\n \"filename\": \"deploying_code\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Deploying Your Code\",\n \"contents\": \"\\n

Deploying Your Code

\\n

Cloud9 IDE offers many different ways to get your code from your editor to your \\nproduction server. To deploy your code, click on the Deploy button in the \\nProject Bar:

\\n

\\\"The

\\n

We offer tight integration with the following environments:

\\n\\n

Following these links will provide you with more information on code deployment.\\nYou can deploy your code to as many services and servers as you like. Keep in \\nmind that you'll already need an account at those hosting providers before you \\ncan deploy your app to them!

\\n

If you're comfortable with the command line, you can also deploy to several more\\nenvironments, such as:

\\n\\n

Warning:

Before you attempt to deploy your application, make sure that you have \\ncommitted all your changes to version control. Cloud9 deploys for you whatever \\nwas last committed to version control.
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"deploying_to_heroku\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Deploying to Heroku\",\n \"contents\": \"\\n

Deploying to Heroku

\\n

This section will show you how to deploy your applications to Heroku, a cloud-based application platform. The integration with Cloud9 IDE makes your development process even more agile. If you don't have a Heroku account, visit their website to create one for free.

\\n

To get started, create a simple Node.js application. If you don't have one yet, you can follow our tutorial on developing one.

\\n

After you click on the Deploy button in the Project Bar, click the plus sign next to Deploy to add another deploy target. Choose Heroku as an option. After you have signed into your Heroku account, you can create a new deploy target or choose an existing one from your account:

\\n

\\\"Showing

\\n

Note:

Heroku only allows you to create names for your apps that contain letters and dashes.\\n\\n
\\n

Next, press Deploy to continue the process; the following window might appear:

\\n

\\\"Dialog

\\n

Heroku Node.js apps are required to have a package.json file, much like with NPM. Cloud9 can generate a package.json file for you, containing metadata to share Heroku. The following lines represent what that file might looks like:

\\n
{\\n    \\\"name\\\": \\\"cloud9-heroku-example\\\",\\n    \\\"version\\\": \\\"0.0.1\\\"\\n}
\\n

After you have a package.json file, you might see this dialog:

\\n

\\\"Dialog

\\n

Sometimes, a Heroku app also requires a Procfile. The Procfile is needed to start the application in Heroku. You can just create a new file, add the line below, and save it as 'Procfile'. Don't add any file extensions.

\\n
web: node web.js
\\n

Try the deploy button again. The console will directly output the following when the deployment is completed:

\\n

\\\"Console

\\n

And just like that, you've deployed your project to Heroku.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"deploying_to_windows_azure_sites\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Deploying to Windows Azure Sites\",\n \"contents\": \"\\n

Deploying to Windows Azure Sites

\\n

This article will show you how to deploy your applications to Windows Azure. If you don't have an account yet, the Windows Azure process will help you create one. Keep in mind that Windows Azure is not free, though it does come with a free trial. Windows Azure projects can be deployed from any operating system.

\\n

To get started, create a simple Node.js application. If you don't have one yet, you can follow our tutorial on developing one.

\\n

After you click on the Deploy button in the Project Bar, click the plus sign next to Deploy to add another deploy target. Choose Windows Azure as an option. You'll be prompted with this dialog:
\\\"Windows

\\n

You must click on the Download Windows Azure Settings button before you can continue. If you don't have a Windows Azure account, here is where you can create one. If you do have an account, your browser will automatically download the required file.

\\n

When that's finished, simply select the downloaded file from your computer, and upload it to Cloud9. You'll only have to do this process once. If you ever need to upload a new certificate, be sure to click Clear cert in the lower-right corner of this dialog.

\\n

After the file has uploaded, click on Create new to create a new hosted service. A hosted service is the container in which your application is hosted when it is deployed to Windows Azure. For more information, see Overview of Creating a Hosted Service for Windows Azure.

\\n

You can set a few configuration options such as the number of instances to use, its host OS, and where the data center is located. Selecting "Enable RDP" and providing a username and password enables remote desktop for your deployment.

\\n

Your new Windows Azure server will appear in the Deploy list:
\\\"Windows

\\n

Go ahead and click on DEPLOY. If this is the first time you're trying to deploy this project to Windows Azure, you'll receive three prompts:

\\n
    \\n

  1. A dialog will inform you of a missing web.config file. If you click Yes, Cloud9 will create a file called Web.cloud.config in your project. This file contains configuration information about your app.

    \\n
    2. \\n

  2. You'll be told about a missing csdef file. If you click Yes, Cloud9 will create a file called ServiceDefinition.csdef in your project. ServiceDefinition.csdef is a Windows Azure-specific files necessary for publishing your application For more information, see Overview of Creating a Hosted Service for Windows Azure.

    \\n
    3. \\n

  3. You'll be asked to select the instance size for this application. For this tutorial, just select Small, and then click Create. For more details about Windows Azure VM sizes, see How to Configure Virtual Machine Sizes.

    \\n
    4. \\n
\\n

Your app will now deploy to a Windows Azure server! You can follow its progress in the Deploy panel, or by watching the messages in the console:\\n\\\"Windows

\\n

For more information on configuring your app on the Windows Azure website, see Deploying a Windows Azure App from Cloud9.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"deploying_via_cli\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Deploying via the Command Line\",\n \"contents\": \"\\n
\\n

Deploying via the Command Line

\\n

In the new version of Cloud9 we don't have support for deployment from the UI yet, but we're going to add those features soon.

\\n

Until then, you can manually install various command-line tools into your workspace and deploy using the command line. \\nIt should go without saying that this is for super 31337 developers that aren't afraid of the command line.

\\n

Below is a list of some of the services we have tested and support deploying to. \\nAll the commands need to be executed in the terminal unless stated otherwise.

\\n

Heroku

\\n

Heroku's toolbelt is installed by default in new VMs.

\\n

Now, you can use the heroku command for your projects, as described in the \\nHeroku documentation.

\\n

If deploying to Heroku, you should probably be using a local instance of PostgresQL, or you may run into problems caused by different database interpretations of SQL.

\\n

Windows Azure Web Sites

\\n

Free and Premium Plans

\\n

In the Console or a Terminal, type the \\nfollowing:

\\n
npm install azure
\\n

Now, you can use the azure command from the Console/Terminal. For more \\ninformation, read the official azure documentation.

\\n

Premium Plans

\\n

To deploy to Azure sites from the command line, open the Terminal and type:

\\n
cd ~/lib/azure-sites\\nnpm install
\\n

Then, add the bin to your workspace's path:

\\n
PATH=$PATH:$HOME/lib/azure-sites/bin
\\n

Now, you can use the azure command in the terminal.

\\n

Windows Azure Cloud Services

\\n

For free and premium plans, follow the instructions on the \\nazure-cmdlet-node repository. This \\nproject is maintained by Cloud9.

\\n

Google App Engine

\\n

First, setup Push to Deploy: Create a new App Engine application at \\ncloud.google.com/console, and then enable \\nPush-to-Deploy under 'App Engine' in the Application Settings page. Leave this \\ntab open to note the URL for your repo.

\\n

Secondly, configure Cloud9. Run the following commands (making sure to replace \\nyour email address, auth-token, and repo-url):

\\n
echo \\\"machine code.google.com login EMAIL password PASSWORD\\\" >> ~/.netrc\\ngit remote add appengine REPO
\\n

Note:

The email in this case is the mail address you use to login to your Google\\nApp Engine account and the password is the auth-token generated from the admin\\nconsole, it is not your google password, never type that into a third party tool.\\n'REPO' is the repository URL generated before.\\n\\n
\\n

Finally, do a commit, and a push:

\\n
git commit -a -m \\\"First commit\\\"\\ngit push appengine master
\\n

OpenShift

\\n
# Install rhc:\\ngem install rhc\\nrhc setup\\n\\n# After this you can use rhc to manage your account:\\n\\n# list apps:\\nrhc apps\\n# To show what you can do with apps do:\\nrhc app help\\n# You deploy via a git push\\ngit push <giturl> master
\\n

CloudFoundry

\\n

To deploy to CloudFoundry from the command line in the Console \\nor a Terminal, type:

\\n
cd ~\\nwget https://github.com/cloudfoundry/vmc/zipball/master\\nmv master cloudfoundry\\nunzip cloudfoundry\\ncd cloudfoundry-vmc-nnnn\\nbundle
\\n

NodeJitsu

\\n

Free and Premium Plans

\\n

In the the Console or a Terminal, type:

\\n
npm install jitsu@0.7.x -g\\nmkdir node_modules\\nmv ../lib/node_modules/jitsu node_modules
\\n

Now, you can run jitsu from the command line. For more information, see \\nthe official jitsu documentation.

\\n

Premium Plans

\\n
npm install jitsu@0.7.x -g
\\n

You can now run jitsu from both the Console and the Terminal.

\\n

Modulus

\\n

In the the Console or a Terminal, type:

\\n
npm install modulus -g
\\n

Now, you can run modulus from the command line. For more information, see \\nthe official modulus documentation.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"faq_general\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"FAQ: General\",\n \"contents\": \"\\n
\\n

FAQ: General

\\n

Can I use FTP workspaces on Cloud9?

\\n

Yes, Cloud9 supports FTP workspaces that allow you to edit your files directly on your FTP server. \\nCurrently FTP workspaces still open in the old version of Cloud9, but soon we'll also support FTP workspaces with the new version of Cloud9.

\\n

One thing that was removed for reliability reasons in the new version of Cloud9, is the ability to deploy over FTP from a regular workspace.\\nWe're bringing back those features in a new format and with much higher reliability in the coming months.

\\n

How do I deploy to Heroku/Openshift/Azure/...?

\\n

See Deploying via CLI.

\\n

Can I connect to SMTP servers (port 25)?

\\n

No, this is not supported by our hosting platform. It does currently allow access to the GMail servers though, so you can use that service during development.

\\n

My workspace says it's out of quota. how do I fix it?

\\n

You can inspect your current quota usage with the df command in the Terminal:

\\n
df
\\n

To find which files and directories are consuming a lot of space, go to a directory such as your home directory, and run this command:

\\n
du -m -d 1 -a | sort -n
\\n

This should give you a list of all members of that directory and how much space they use in megabytes.

\\n

Alternatively, try du-c9 for seeing all files you added to your workspace and account for the quota.

\\n

I can't preview my running app.

\\n

Try using port 8080 instead, which often solves this case.

\\n

How can I upload local files to my project?

\\n

Either drag a local file directly from your desktop into the Cloud9 file tree,\\nor use the "File > Upload Local Files" menu item.

\\n

How can I download my project files?

\\n

Use "File > Download project". Currently, this will give you a .tar.gz file, which\\nensures maximum portability. To open these files, you can use something like\\nWinRAR or 7-zip.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"faq_php\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"FAQ: PHP\",\n \"contents\": \"\\n
\\n

FAQ: PHP

\\n

where are the Apache logs?

\\n

By default the logs are in ~/lib/apache2/log

\\n

Is mail() supported?

\\n

No, this is currently not supported; see FAQ: General about SMTP access.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"faq_python\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"FAQ: Python\",\n \"contents\": \"\\n
\\n

FAQ: Python

\\n

Why does easy_install report a permission_denied error?

\\n

Please use sudo easy_install instead.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"faq_ssh\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"FAQ: SSH workspaces\",\n \"contents\": \"\\n
\\n

FAQ: SSH workspaces

\\n

I cannot create a SSH workspace using a Digital Ocean droplet

\\n

We recently discovered our web host is blocking connections to some Digital Ocean IP addresses because they suspect they are being used by Iranian users. They are legally forced to block them.

\\n

Digital Ocean maintains a whitelist of droplet IP addresses which should not be blocked and our web host follows this list.

\\n

Please raise a support ticket with Digital Ocean mentioning that you would like to have your droplet IP added to the whitelist. After this is complete you will be able to create your SSH workspace within 24 - 48 hours.

\\n

I'm getting an error on the SSH install script: "ncurses not found"

\\n

Try executing the following command:

\\n
yum install ncurses-devel
\\n

or

\\n
yum install glibc-static
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"autocompletion\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Code Autocompletion\",\n \"contents\": \"\\n

Code Autocompletion

\\n

For Javascript programs, Cloud9 IDE provides intelligent and responsive autocompletion for your code. Autocompletion is based not only on the content within your files, but also on the ECMAScript and Node.js standard library:

\\n

\\\"Autocompletion

\\n

Methods defined in ECMAScript and Node.js also have documentation provided for you. Simply hover over a method name for a moment, and a second box quickly shows some additional information.

\\n

You can disable autocompletion in the Settings menu.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"collaboration\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Collaboration\",\n \"contents\": \"\\n
\\n

Collaboration

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n

Collaboration with Cloud9 IDE is an amazing feature that lets you do more than just share your projects with any other Cloud9 developer. You can grant someone else access to change files in your workspace, in realtime--or just let them view the workspace without any other rights. While you're collaborating, you can discuss the code through a built-in chat room.

\\n

To invite someone to collaborate on a project with you, simply copy the URL in the browser and send it to a friend. You can also click on Share in the menu bar to get quick access to other ways to share, such as via e-mail, Twitter, or Facebook.

\\n

Let's take a look at some of the additional features available while you collaborate.

\\n

Members List

\\n

There are two terms used for people accessing your project: members and visitors. Members are individuals that have read and write access to your project--that means they can change any code; visitors only have read access. The Members panel lists all the collaborators in a project, both active and inactive:

\\n

\\\"The

\\n

If you are the owner of a project, you can click on anyone's username to grant (or revoke) write access:

\\n

\\\"Granting

\\n

If you're worried about the sanctity of your code after grant access to other developers, fear not. You can always take a look at a file revision history to view line-by-line changes made to your project over time.

\\n

Chatting

\\n

Any member or visitor can participate in group chat with each other. Developers can also choose to double-click on a person's username and engage in a private, instant-message-style conversation.

\\n

Collaborate on Code

\\n

When a collaborator changes a file you're also working on, Cloud9 detects it and asks you whether you'd like to use their changes, or your version. We're also simply giving you the option to merge both, using a three-way-merge algorithm to handle any conflicts. This is the same algorithm used by version control systems like git for merging branches.

\\n

To make the experience even smoother you can choose "Always merge by default" and we'll never interrupt you about file changes again.

\\n

Check out the video below to see this in action.

\\n
\\n\\n
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"colorpicker\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Color Picker\",\n \"contents\": \"\\n

Color Picker

\\n

Note:

this feature is deprecated\\n\\n
\\n
\\n\\n
\\n\\n

The color picker is an awesome feature in Cloud9 IDE, designed to not only make color selections easier, but also, more harmonious. At its core, the color picker is a way to represent words (red, blue, e.t.c.), RGBA values (rgba(175, 3, 124, .6)), or hex values (#f00f00) into actual colors.

\\n

To enable the color picker, flip the preferences on in the Settings panel. You can use the color picker in CSS, SVG, HTML, or APF Skin files. All you have to do is hover over the value of a color definition, and it'll instantly highlight, like this: \\\"Color

\\n

When the represented color is highlighted, click on it. You'll get a color square defining all the possible color arrangements. To select a color, you can click in the square, pick your own RGB or HSB values, or enter some hex code. Best of all, at the bottom of the window, you'll find a list of other colors found within the same document--just in case you want to achieve matching shades:
\\\"Color

\\n

To set the value, just click anywhere outside of the color picker.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"git_blame\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Git Blame\",\n \"contents\": \"\\n

Git Blame

\\n

Note:

this feature is deprecated\\n\\n
\\n
\\n\\n
\\n\\n

When you're working with git repositories, it's helpful to know who made a commit to a particular piece of code. As it turns out, git has a feature called git blame that we've integrated directly into Cloud9 IDE.

\\n

By using git blame, you'll be able to instantly discover who edited certain lines of code, when they edited it, and what their commit message at the time was. Clicking on a git commit also highlights other lines of code changed at the same time. To launch the git blame feature, open a file and navigate to Tools > Git > Blame.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"custom_runners\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Custom Runners\",\n \"contents\": \"\\n
\\n

Custom Runners

\\n

Luckily you're not limited to the default set of Runners in Cloud9.\\nYou can simply define your own custom Runner, which is both simple and very powerful.\\nAll you need to do is create a Runner file.\\nIn this article we'll describe how to do this in just a few steps.

\\n

In the Run panel (usually at the bottom of the UI), click the 'Runner' text input and choose 'New Runner'. \\nIn the new Runner file that's now opened, you can configure your runner\\nusing a simple JSON format. We'll show a basic example below\\nand then explain the different properties you can use.

\\n

Let's start with a basic example: a runner for go files.

\\n
{\\n    \\\"cmd\\\": [\\\"go\\\", \\\"run\\\", \\\"$file\\\", \\\"$args\\\"],\\n    \\\"selector\\\": \\\"source.go\\\",\\n    \\\"info\\\": \\\"Your code is running :)\\\"\\n}
\\n

This runner will use "go run" for any file that has a ".go" file extension.\\nIf you add it, it'll override our default Go runner.

\\n

As another example, let's save a new Node 0.11 configuration, including Harmony support. \\nCreate a new Runner, add this code, and save it as 'Node 0.11.x.run':

\\n
// This file overrides the built-in Node 0.11.x runner\\n// For more information see http://docs.c9.io:8080/#!/api/run-method-run\\n{\\n  \\\"cmd\\\": [\\n    \\\"bash\\\",\\n    \\\"--login\\\",\\n    \\\"-c\\\",\\n    \\\"nvm use 0.11 > /dev/null; node --harmony ${debug?--nocrankshaft --nolazy --debug-brk=15454} '$file' $args\\\"\\n  ],\\n  \\\"debugger\\\": \\\"v8\\\",\\n  \\\"debugport\\\": 15454,\\n  \\\"info\\\": \\\"Your code is running at \\\\\\\\033[01;34m$url\\\\\\\\033[00m.\\\\n\\\\\\\\033[01;31mImportant:\\\\\\\\033[00m use \\\\\\\\033[01;32mprocess.env.PORT\\\\\\\\033[00m as the port and \\\\\\\\033[01;32mprocess.env.IP\\\\\\\\033[00m as the host in your scripts!\\\\n\\\"\\n}
\\n

Note:

alternatively, you can check 'Show Hidden Files' in your workspace directory tree (the small gear in the upper right corner), and create a new file in the '.c9/runners' folder called 'Node 0.11.x.run' with this code.\\n\\n
\\n

That's it! Your custom Runner should be available in the Run panel.

\\n

Runner Variables

\\n

Here's a list of all the variables you can use in your runners:

\\n
    \\n

  • $file_path The directory of the current file, e. g., /home/ubuntu/workspace/docs

    \\n
    • \\n

  • $file The full path to the current file, e. g., /home/ubuntu/workspace/docs/Chapter1.txt.

    \\n
    • \\n

  • $args Any arguments entered after the file name.

    \\n
    • \\n

  • $file_name The name portion of the current file, e. g., Chapter1.txt.

    \\n
    • \\n

  • $file_extension The extension portion of the current file, e. g., txt.

    \\n
    • \\n

  • $file_base_name The name only portion of the current file, e. g., Document.

    \\n
    • \\n

  • $packages The full path to the Packages folder.

    \\n
    • \\n

  • $project The full path to the current project file.

    \\n
    • \\n

  • $project_path The directory of the current project file.

    \\n
    • \\n

  • $project_name The name portion of the current project file.

    \\n
    • \\n

  • $project_extension The extension portion of the current project file.

    \\n
    • \\n

  • $project_base_name The name only portion of the current project file.

    \\n
    • \\n

  • $hostname The hostname of the workspace.

    \\n
    • \\n

  • $hostname_path The hostname of the workspace together with the relative path of the project file.

    \\n
    • \\n

  • $url The full url to access the workspace.

    \\n
    • \\n

  • $port The port assigned to the workspace.

    \\n
    • \\n

  • $ip The ip address to run a process against in the workspace.

    \\n
    • \\n
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"gotofile_and_definition\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Using Goto File and Goto Definition\",\n \"contents\": \"\\n

Using Goto File and Goto Definition

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n
\\n\\n
\\n\\n

Let's say you're working a large project containing many files, and you kind-of sort-of know the name of a file that you want to open up. Goto File is our feature to help you quickly and easily jump to any file in your workspace, without the need to search through different directories. Simply hit Cmd-E (or Ctrl-E on Unix/Windows) and away you go:

\\n

\\\"Goto

\\n

Goto File offers filtering for any portion of a filename, including directories. Search for the beginning, middle, or end of a file path, or even just an extension, like .js, and Goto File with instantly present the results to you. Clicking on a name in the list opens the file right up. Goto File does not support case-insensitive, wildcard (*, ?), or regular expression (., +) searching.

\\n

Goto Definition takes the same concept and applies it to files. You can easily navigate between classes and members defined in your files. By entering text, you can filter your class' member results. Finally, as you navigate through your file, Cloud9 IDE will jump to the relevant portion of the code:

\\n

\\\"Goto

\\n

Note:

Currently, Goto Definition only works for Javascript files.\\n\\n
\\n

Another feature that's available is the capability to "jump to definition." If your cursor is on a variable or function name, you can tap F12 (or type jumptodef in the console) to instantly scroll the editor to the member's definition.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"language_analysis\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Language Analysis\",\n \"contents\": \"\\n
\\n

Language Analysis

\\n

For JavaScript files, Cloud9 provides analysis using a combination of our own analysis tools, as well as JSHint (specifically for Javascript code). Our language analysis can't detect if your program is correct, fast, or has memory leaks, but it can save you time by spotting things like undeclared variables, syntax errors, or other preventable typos.

\\n

When Cloud9 detects an issue with your code, an icon appears in the gutter for the offending lines of code. There are three types of identifiers available for your code:

\\n
    \\n
  • Informational (\\\"Little): these are non-critical, non-dangerous updates about your code
    • \\n
  • Warnings (\\\"Warning): these are potentially incorrect pieces of code
    • \\n
  • Errors (\\\"Error): these are incorrect lines of code that will almost certainly throw a runtime error when you try to run your script
    • \\n
\\n

If you hover over any of these icons in the gutter, you'll get a pop-up that presents some information as to what, exactly, the problem is. For example, suppose we have a variable declared, called fs, that is never used:
\\\"fs

\\n

Notice also that fs has a strikethrough, to provide further visual clues that something is not quite right.

\\n

If you're concerned with the level of information that's listed in the gutter, you can always configure its "strictness" in the IDE preferences. For example, you could choose to hide every icon that isn't a warning or an error.

\\n

Configuring Global Options

\\n

JSHint provides additional configuration options that Cloud9 incorporates on a per-file basis. Typically, you declare these options as comments at the very top of a file, like this:

\\n
/*jshint curly:true, debug:true */
\\n

For a full list of the JSHint configutation options, please check the documentation page describing them.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"multiple_cursors\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Multiple Cursors\",\n \"contents\": \"\\n

Multiple Cursors

\\n

Multiple cursors is one of the most useful features available in the Cloud9 editor. You can use multiple cursors to perform tasks like rename several variables or members at once, break up lists separated by commas, or insert the same text in multiple locations.

\\n

\\\"Showing

\\n

Multiple selections can be copied and pasted, and you can insert or remove entire lines in several locations.

\\n

There are several ways to get access to mutliple cursors:

\\n
    \\n
  • Via keyboard shortcuts, you can create a new cursor in any direction
    • \\n
  • By holding the Alt key, clicking the mouse, and dragging the cursor up or down in the editor
    • \\n
  • Through the menu bar at Selection > Multiple Selections
    • \\n
\\n

One of the best capabilities is the ability to instantly select the next instance of your currently highlighted section. This is especially useful for refactoring several parts of the code at once. To do this, press Ctrl-Alt, followed by the right (or left) arrow key to navigate around in the code.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"revisions\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Revisions\",\n \"contents\": \"\\n

Revisions

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n
\\n\\n
\\n\\n

Every time you save a file on Cloud9, a diff of any changes made to it is saved by the server. Over time, you can view these file revisions as content is added and removed from your files. You can also restore a file to any previously saved state; you'll never have to worry about losing your work ever again!

\\n

To access file revisions, you can either go to File > File Revisions History, or type Cmd-B on Mac or Ctrl-B on Linux/Windows. This will pop open the Revisions History panel. Red lines indicate lines that were removed; green lines indicate lines that were either added or changed.

\\n

At the bottom of the panel, there's a checkbox for showing all of a file's changes. Files changes that occur relatively soon to one another--say, a few seconds--are grouped by the revisions panel as one "change." If you prefer to see every single change as an individual entry, enable the Show all file changes checkbox.

\\n

To restore a file to a previous revision, simply click the revisions button for that entry: \\\"Revisions

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"searching_in_files\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Searching and Replacing in Files\",\n \"contents\": \"\\n
\\n

Searching and Replacing in Files

\\n
\\n\\n
\\n\\n

Aside from Goto File and Goto Definition, Cloud9 also offers more traditional search functionality. There are three types of search modes available: quicksearch, search and replace, and find in files.

\\n

Quicksearch

\\n

Quicksearch can be activated by hitting Cmd-F on a Mac, or Ctrl-F on a Unix/Windows machine. As you type in the quicksearch bar, the IDE instantly shifts to the next available result. This is a great way to quickly search around in your code without hassle.

\\n

Quicksearch offers the following options:

\\n
    \\n
  • Regular Expressions: when enabled, your search is treated as a regular expression
    • \\n
  • Match Case: when enabled, your search takes capitalizations seriously:
    • \\n
  • Whole Words: when enabled, your search will only be considered for whole words:
    • \\n
  • Search Backwards: when enabled, the search goes backwards, instead of forwards
    • \\n
  • Wrap Around: when enabled, the search loops around the file, from bottom to top
    • \\n
  • Search Selection: when enabled, the search only considers code that you've currently highlighted
    • \\n
\\n

Search and Replace

\\n

Building on the features of quicksearch, search and replace allows you to replace segments of code in your file. You can again continue to use regular expressions, keeping in mind the groupings are prefixed with a dollar sign, i.e. $1.

\\n

Replacing offers two more options:

\\n
    \\n
  • Preserve Case: if enabled, case is preserved while replacing content
    • \\n
  • Highlight Matches: if enabled, the new replaced matches are highlighted in the document
    • \\n
\\n

Find in Files

\\n

In order to search across a set of files, you'll want to use the Find in Files feature. Here, you can search of a string or regular expression, within your entire workspace or a single directory. You can also filter based on extensions, like *.js or *.rb.

\\n

Find in files offers some of the same search options as quicksearch:

\\n
    \\n
  • Regular Expressions: when enabled, your search is treated as a regular expression
    • \\n
  • Match Case: when enabled, your search takes capitalizations seriously
    • \\n
  • Whole Words: when enabled, your search will only be considered for whole words
    • \\n
\\n

One more feature of find in files is the ability to render search results either in the console or the IDE. You can fold results to keep them out of the way, or, edited the file if you're working down a list:
\\\"Search

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"supported_languages\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Supported Languages\",\n \"contents\": \"\\n
\\n

Supported Languages

\\n

Cloud9 IDE has varying levels of support for different programming languages. \\nUsually you will at least have Syntax Highlighting in the editor and the ability\\nto run apps from the Terminal.

\\n

Syntax Highlighting

\\n

Cloud9 IDE develops and builds on Ace, an \\neditor for writing code online. Cloud9's Ace editor currently supports \\nhighlighting for about 100 programming languages, and any changes made to Ace are \\nreflected back into Cloud9 IDE.

\\n

The list of supported languages is growing, and you can get the full list from \\nthe View > Syntax menu. Feel free to create an issue in the Ace repository \\nfor new requests, or add your own syntax highlighting mode.

\\n

See Syntax Highlighting & Themes for more \\ninfo.

\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n

Running apps

\\n

The Run panel currently supports running the following by default:

\\n
    \\n
  • Apache httpd (PHP, HTML)
    • \\n
  • Node
    • \\n
  • Python
    • \\n
  • Ruby
    • \\n
  • Ruby on Rails
    • \\n
  • Go
    • \\n
  • CoffeeScript
    • \\n
  • Julia
    • \\n
  • Mocha
    • \\n
  • Shell script
    • \\n
\\n

If you'd like to run any other language, simply create a new "Runner".

\\n

You can also do so from the Terminal. \\nEach workspace is an Ubuntu VM with the standard tools like bash, make, \\ngcc, vim, java SDK or perl pre-installed.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"syntax_highlighting_themes\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Syntax Higlighting and Themes\",\n \"contents\": \"\\n

Syntax Higlighting and Themes

\\n
\\n\\n

Cloud9 IDE develops and builds on Ace, an editor for writing code online. Ace supports over two dozen different themes for highlighting your code, and any changes made to Ace are reflected back into Cloud9 IDE.

\\n

You can change your current theme by going to View > Themes, and selecting from one of the many options. By hovering over the menu items, you'll be able to get a preview of the theme. To activate a theme you like, just click on its name.

\\n

The IDE contains the following themes:

\\n
    \\n
  • Chrome
    • \\n
  • Clouds
    • \\n
  • Clouds Midnight
    • \\n
  • Cobalt
    • \\n
  • Crimson Editor
    • \\n
  • Dawn
    • \\n
  • Eclipse
    • \\n
  • Idle Fingers
    • \\n
  • Kr Theme
    • \\n
  • Merbivore
    • \\n
  • Merbivore Soft
    • \\n
  • Mono Industrial
    • \\n
  • Monokai
    • \\n
  • Pastel On Dark
    • \\n
  • Solarized Dark
    • \\n
  • Solarized Light
    • \\n
  • TextMate
    • \\n
  • Tomorrow
    • \\n
  • Tomorrow Night
    • \\n
  • Tomorrow Night Blue
    • \\n
  • Tomorrow Night Bright
    • \\n
  • Tomorrow Night Eighties
    • \\n
  • Twilight
    • \\n
  • Vibrant Ink
    • \\n
\\n

By default, files are highlighted based on their file extension. You can change this by going to View > Syntax, and selecting a different context. This forces a single file to use a different highlighter.

\\n

We support highlighting for at least the following languages, and many more:

\\n
    \\n
  • CoffeeScript
    • \\n
  • ColdFusion
    • \\n
  • C#
    • \\n
  • CSS
    • \\n
  • Go
    • \\n
  • Groovy
    • \\n
  • haXe
    • \\n
  • HTML
    • \\n
  • C/C++
    • \\n
  • Clojure
    • \\n
  • Java
    • \\n
  • JavaScript
    • \\n
  • JSON
    • \\n
  • LaTeX
    • \\n
  • LESS
    • \\n
  • Liquid
    • \\n
  • Lua
    • \\n
  • Markdown
    • \\n
  • OCaml
    • \\n
  • Perl
    • \\n
  • pgSQL
    • \\n
  • PHP
    • \\n
  • Powershell
    • \\n
  • Python
    • \\n
  • Ruby
    • \\n
  • OpenSCAD
    • \\n
  • Scala
    • \\n
  • SCSS
    • \\n
  • SH
    • \\n
  • SQL
    • \\n
  • SVG
    • \\n
  • Text
    • \\n
  • Textile
    • \\n
  • XML
    • \\n
  • XQuery
    • \\n
  • YAML
    • \\n
\\n

We are always adding new themes and new languages to support, so check the menu often! Since we use Ace to provide syntax highlighting, feel free to log an issue there for new requests.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"uploading_downloading\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Uploading and Downloading Workspace Files\",\n \"contents\": \"\\n

Uploading and Downloading Workspace Files

\\n

Cloud9 IDE allows you to easily add files to your curent workspace at any time. You can drag and drop files from your computer directly into the Project Files pane, and the IDE will add them to your project. Google Chrome users can also drag entire folders into the IDE.

\\n

If a file transfer is halted for some reason--say, if you lose your internet connection--the upload resumes once the connection returns. As the files transfer, the IDE lets you know the current status of the overall transfer, as well as the status of each file being uploaded:

\\n

\\\"Uploading

\\n

You can also get an exact copy of your workspace to save on your computer. By going into File > Download Project, you will be provided with a Zip file containing the entirety of your project.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"zen_mode\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Activating Zen Mode\",\n \"contents\": \"\\n

Activating Zen Mode

\\n

Note:

this feature is deprecated\\n\\n
\\n
\\n\\n
\\n\\n

Zen mode is a full screen coding environment designed to make you more productive. It essentially removes all the additional UI elements in Cloud9 IDE, and places you in a harmonious relationship with your code.

\\n

To activate zen mode, simply hover over the upper right corner of the code editor, and click the icon that appears. Keep in mind that you'll need to have a file open before you can launch zen mode. You can resize your window by holding and dragging the left or right border.

\\n

To get out of zen mode, hover over the same corner and click the same icon.

\\n

You can also enter and exit zen mode via keyboard shortcuts, command line, or from the menu bar at View > Zen Mode.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_drupal\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Framework: Drupal\",\n \"contents\": \"\\n

Framework: Drupal

\\n

For Drupal there are some installation guides around which tell you to install PHP first, but that's not necessary with Cloud9.\\nYou don't need to install MySQL either, it is already preinstalled in PHP workspaces. \\nJust make a new workspace, choose PHP, go to the Terminal, and execute the following:

\\n
cd $HOME\\ncurl -O http://ftp.drupal.org/files/projects/drupal-7.30.tar.gz\\ntar xvf drupal-7.30.tar.gz\\nmv drupal-7.30/* workspace/\\nmv drupal-7.30/.htaccess workspace/\\ncd $HOME/workspace\\nmysql-ctl install\\nmysql-ctl start\\nmysql-ctl status
\\n

Open the file install.php in the file tree, and while opened, click on the "Run Project" button in the menu bar on top of the IDE.\\nAn URL will be shown at the bottom of the page, something like "https://drupal-c9-lcipriani.c9.io/", but with your username and workspace name in it.

\\n

Copy the url in a new browser tab and you will see the install page of Drupal

\\n

You can now proceed with the installer

\\n

\\\"Drupal

\\n

Now be careful inserting the correct values for the database. You need to change the values as follows:

\\n
user: yourusername\\ndatabase: c9\\nhost: 127.0.0.1
\\n

Note:

localhost will not work, while 127.0.0.1 will.\\n\\n
\\n

Open the Advanced Options in the database settings page as shown in the screenshot:

\\n

\\\"Drupal

\\n

Now fill the form with the correct site information:

\\n

\\\"Drupal

\\n

Continue the setup and enjoy your website!

\\n

Note:

if you are not able to load CSS, access your website WITHOUT using https, but use simple http; in another tab open the url: http://drupal-c9-lcipriani.c9.io/\\n\\n
\\n

\\\"Drupal

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_angularjs\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Framework AngularJS\",\n \"contents\": \"\\n

Framework AngularJS

\\n

AngularJS lets you write client-side web \\napplications as if you had a smarter browser.

\\n

Follow these steps to create an AngularJS application using the official project\\ntemplate:

\\n
    \\n
  1. Create a workspace and choose the PHP workspace type
    2. \\n
  2. Open a Terminal, or using the pre-existing one at the bottom
    3. \\n
  3. Run the following commands in the Terminal:
    rm -rf * .c9\\ngit clone https://github.com/angular/angular-seed.git .\\nnpm install\\nmv package.json package.json.bak\\njq '.scripts.start=\\\"http-server -a $IP -p $PORT\\\"' package.json.bak > package.json
    \\n
    4. \\n
  4. Click the Run Project button in the top menu of the IDE
    5. \\n
  5. Check the README.md for further steps
    6. \\n
\\n

Note:

We are choosing the PHP workspace type to in order to have the Apache runner\\nas a default so you can just click Run Project to get started. This doesn't\\nlimit the choice of the backend technology you might want to use.
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_express\",\n \"mtime\": 1416496691000,\n \"pageTitle\": \"Framework: Express\",\n \"contents\": \"\\n
\\n

Framework: Express

\\n

Express is a minimal and flexible Node.js web application framework that provides a robust set of features for web and mobile applications.

\\n

To get started with an Express app, first create a workspace and choose either the Node.js type, or a Custom workspace type for a clean workspace. Open the new workspace (or an existing one) to follow the instructions below.

\\n

Installation

\\n

First we'll install the Express project generator and generate an application stub:

\\n
$ npm install -g express-generator\\n$ express -f .\\n$ npm install
\\n

You might want to take a look at package.json and update the application name from the default workspace to something more fitting.

\\n

Running

\\n

Now you have a fully configured express application already. You can run it from the terminal using:

\\n
$ bin/www
\\n

Now if you click the Preview button in the top menu in the IDE, and choose "Preview with Web Server", this will open the Preview window for your running app.

\\n

Creating a Run Configuration

\\n

In order to make life easier you can create a run configuration for express.

\\n
    \\n
  1. Click Run -> Run Configurations -> Manage ...
    2. \\n
  2. Click Add New Config
    3. \\n
  3. In the run panel fill in Express as name, bin/www as the command and Node 0.10.x as the runner.
    4. \\n
  4. You can optionally make this run configuration the default runner by clicking Set As Default. If you do so then clicking the run button will always run the app and not the currently opened file.
    5. \\n
\\n

The finished run configuration should look something like this

\\n

\\\"Express

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_ghost\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Framework: Ghost\",\n \"contents\": \"\\n

Framework: Ghost

\\n

Ghost is a simple, powerful publishing platform that \\nallows you to share your story with the world.

\\n

Create a Ghost blog as follows:

\\n
    \\n
  1. Create a new workspace (Node.js or Custom for a clean workspace)
    2. \\n
  2. Open a Terminal, or use the pre-existing one at the bottom
    3. \\n

  3. Run the following commands in the Terminal:

    \\n
     $ curl -L https://ghost.org/zip/ghost-latest.zip -o ghost.zip\\n $ unzip -uo ghost.zip -d .\\n $ rm ghost.zip\\n $ npm install --production
    \\n
    4. \\n

  4. Adapt the config.js file to the Cloud9 environment. Change the following keys:

    \\n
     config: {\\n     development: {\\n         url: 'https://' + process.env.C9_HOSTNAME,\\n     },\\n     server: {\\n         host: process.env.IP,\\n         port: process.env.PORT\\n     }\\n }
    \\n
    5. \\n

  5. Run Ghost by typing npm start in the console or by opening index.js and\\nhitting the run button.

    \\n
    6. \\n
  6. Click the "Preview" button in the top menu in the IDE, and choose \\n"Preview with Web Server". This will open the Preview window for your newly setup Ghost blog
    7. \\n
\\n

Change the URL to /ghost and create your admin user to login to the Ghost admin interface

\\n

Note:

These instructions are based on the official Ghost Installation Guide\\n
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_ionic\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Framework: Ionic\",\n \"contents\": \"\\n

Framework: Ionic

\\n

Ionic is an open source front-end framework for developing hybrid mobile apps with HTML5.

\\n

Create a Ionic app as follows:

\\n
    \\n
  1. Create a new workspace (Node.js or Custom for a clean workspace)
    2. \\n
  2. Open a Terminal, or use the pre-existing one at the bottom
    3. \\n

  3. Run the following commands in the Terminal:

    \\n
     $ npm install -g cordova ionic\\n $ ionic start myApp sidemenu\\n $ cd myApp\\n $ ionic serve $PORT
    \\n
    4. \\n

  4. Click the "Preview" button in the top menu in the IDE, and choose "Preview with Web Server". This will open the Preview window for your running app.

    \\n
    5. \\n
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_jekyll\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Framework: Jekyll\",\n \"contents\": \"\\n

Framework: Jekyll

\\n

Jekyll is a great static site generator, also used by github pages. You simply need to install the Ruby gem and then make sure you pass the right port to the serve command.

\\n
$ gem install jekyll\\n$ jekyll new my-awesome-site\\n$ cd my-awesome-site\\n$ jekyll serve --port $PORT
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_joomla\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Joomla\",\n \"contents\": \"\\n
\\n

Joomla

\\n

Joomla is a popular open source CMS. \\nInstalling Joomla is very straightforward, but there are just a few quirks to keep in mind, which we describe below.

\\n

Note:

all instructions here are based on Joomla v3.x.\\n\\n
\\n

Download Joomla

\\n
    \\n
  1. Create a Cloud9 workspace of type "Custom" or "PHP"
    2. \\n

  2. Download and Unzip Joomla from the Terminal. You can find the latest version on the Joomla website

    \\n
     wget http://joomlacode.org/gf/download/frsrelease/19665/160049/Joomla_3.3.3-Stable-Full_Package.zip\\n unzip Joomla*.zip\\n rm Joomla*.zip
    \\n
    3. \\n
\\n

Start the database

\\n

Joomla requires a MySQL database to connect to. MySQL is pre-installed in your workspace, so just execute these commands:

\\n
mysql-ctl install\\nmysql-ctl start
\\n

... and then note the credentials to use in the configuration of Joomla later on.

\\n

Install Joomla

\\n

To run the Joomla installer, open index.php and run it with the "Run" (or "Run Project") button at the top of the IDE.\\nNext, click the URL that's displayed in the Run panel, which looks something like https://joomla-c9-username.c9.io/installation/index.php#. \\nThis will open up the Preview window with the installer.

\\n

Now, here comes the quirky part: the installer will not work properly if it's loaded over HTTPS, as the Cloud9 Preview window does by default.\\nSo, in order to make the Joomla installer work, do the following:

\\n
    \\n
  1. Pop out the Preview by clicking the Popout icon \\\"Preview (or copy & load the URL in a browser tab)
    2. \\n
  2. Change the URL from https:// to http:// and load it
    3. \\n
\\n

Now you should be able you to get through the installer successfully.

\\n

Main configuration

\\n

The main Configuration screen should look like this:

\\n

\\\"Joomla

\\n

Enter whatever values you'd like here.

\\n

Database

\\n

The second quirky and important thing to keep in mind in the Database section, is to use Host Name "0.0.0.0" instead of "localhost".

\\n

So use values like shown in the screenshot below:

\\n

\\\"Joomla

\\n

Finally

\\n

Use whatever settings you'd like in the final installation screen, and after it completes, have Joomla remove the Installation folder for safety.

\\n

That's it, you're done and your Joomla setup should run fully on Cloud9!

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_koa\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Framework: Koa\",\n \"contents\": \"\\n

Framework: Koa

\\n

Koa is a new web framework designed by the team behind Express, which aims to be a smaller, more expressive, and more robust foundation for web applications and APIs.

\\n

To get started with a Koa app, first create a workspace and choose either the Node.js type, or a Custom workspace type for a clean workspace.

\\n

Koa.Js makes use of the new generator feature in javascript ECMA 6. \\nThis feature is support in Node from 0.11 and up by toggling the --harmony flag. \\nBy default Cloud9 runs Node v0.10.x or v0.8.x, depending on your setup, so we first need activate Node version 0.11.x.

\\n

Open a Terminal, or using the pre-existing one at the bottom and execute the following in your Terminal:

\\n
nvm use 0.11
\\n

Next, we need to install Koa itself:

\\n
npm install koa
\\n

Now we can create a simple Koa.Js server.\\nCreate a server.js file in your root folder with this code:

\\n
var koa = require('koa');\\nvar app = koa();\\n\\napp.use(function *(){\\n    this.body = '<h1>Hello from Koa.Js</h1>';\\n});\\n\\napp.listen(process.env.PORT);
\\n

If you now press the Run button on top of the IDE, you will see some errors, as the runner/debugger defaults to 'Node (default)', which is Node version 0.10.x or 0.8.x.

\\n

Luckily all you need is to create a Runner file so Cloud9 can run Node 11.x in harmony mode and thereby support generators.

\\n

In the Run panel below, click the 'Runner' text input and choose 'New Runner'. \\nIn the new Runner file that's opened, save the following code as 'Node 0.11.x.run':

\\n
// This file overrides the built-in Node 0.11.x runner\\n// For more information see http://docs.c9.io:8080/#!/api/run-method-run\\n{\\n  \\\"cmd\\\": [\\n    \\\"bash\\\",\\n    \\\"--login\\\",\\n    \\\"-c\\\",\\n    \\\"nvm use 0.11 > /dev/null; node --harmony ${debug?--nocrankshaft --nolazy --debug-brk=15454} '$file' $args\\\"\\n  ],\\n  \\\"debugger\\\": \\\"v8\\\",\\n  \\\"debugport\\\": 15454,\\n  \\\"info\\\": \\\"Your code is running at \\\\\\\\033[01;34m$url\\\\\\\\033[00m.\\\\n\\\\\\\\033[01;31mImportant:\\\\\\\\033[00m use \\\\\\\\033[01;32mprocess.env.PORT\\\\\\\\033[00m as the port and \\\\\\\\033[01;32mprocess.env.IP\\\\\\\\033[00m as the host in your scripts!\\\\n\\\"\\n}
\\n

Note:

alternatively, you can check 'Show Hidden Files' in your workspace directory tree (the small gear in the upper right corner), and create a new file in the '.c9/runners' folder called 'Node 0.11.x.run' with this code.\\n\\n
\\n

Let's run server.js with this new configuration; in the Run panel on the bottom, choose your new 'Node 0.11.x' Runner, and press Run again.

\\n

You Koa.Js server should now be up and running.

\\n

Now if you click the Preview button in the top menu in the IDE, and choose "Preview with Web Server", this will open the Preview window for your running app.

\\n

(Credits go to Tom at http://kyorcode.blogspot.nl/2014/08/running-koajs-in-cloud9.html)

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_laravel\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Framework: Laravel\",\n \"contents\": \"\\n

Framework: Laravel

\\n

For Laravel there are some installation guides around which tell you to install PHP first, but that's not necessary with Cloud9.\\nJust make a new workspace, choose PHP, go to the Terminal, and execute the following:

\\n
rm README.md php.ini hello-world.php\\ncomposer create-project laravel/laravel ./laravel --prefer-dist\\nshopt -s dotglob\\nmv laravel/* ./\\nrm -rf laravel
\\n

As lavarel is serving its content from the public directory we need to modify the apache config:

\\n
sudo vi /etc/apache2/sites-enabled/001-cloud9.conf
\\n

Then do the following:

\\n
// Change this line\\nDocumentRoot /home/ubuntu/workspace\\n\\n// To following\\nDocumentRoot /home/ubuntu/workspace/public
\\n

Run the project with the "Run Project" button in the menu bar on top of the IDE.\\nIf you click the URL that appears in the Run panel below (in the shape of 'https://laravel-c9-username.c9.io/'), you can preview your new Laravel app.

\\n

\\\"Run

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_meteor\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Framework: Meteor\",\n \"contents\": \"\\n

Framework: Meteor

\\n

Meteor is an open-source platform for building web apps.

\\n

Create a Meteor app as follows:

\\n
    \\n
  1. Create a new workspace (Node.js or Custom for a clean workspace)
    2. \\n
  2. Open a Terminal, or using the pre-existing one at the bottom
    3. \\n

  3. Run the following commands in the Terminal:

    \\n
     curl https://install.meteor.com/ | sh\\n meteor create ./my_cool_app\\n cd my_cool_app/\\n meteor --port $IP:$PORT
    \\n
    4. \\n

  4. Click the Preview button in the top menu in the IDE, and choose "Preview with Web Server". This will open the Preview window for your running app.

    \\n
    5. \\n
\\n

Note:

Alternatively, for the last step, click on the link that's displayed in the terminal, and change it in the resulting Preview to http://127.0.0.1:8080.
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"frameworks_symfony2\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Framework: Symfony2 \",\n \"contents\": \"\\n
\\n

Framework: Symfony2

\\n

Symfony is one of the leading PHP Webframeworks. It is Open-Source and built on top of the Symfony Components.

\\n

Getting started

\\n
    \\n
  1. Create a Cloud9 workspace of the type "Custom" or "PHP"
    2. \\n

  2. Install the Intl extension for PHP that is required in most of the Symfony2 projects

    \\n
     sudo apt-get install php5-intl
    \\n
    3. \\n

  3. Set a valid PHP timezone

    \\n
     echo 'date.timezone = UTC' | sudo tee --append /etc/php5/apache2/php.ini
    \\n
    4. \\n

  4. Starting MySQL-Server

    \\n
     sudo mysql-ctl install\\n sudo mysql-ctl start
    \\n
    5. \\n
\\n

Create a Symfony-Project

\\n

Open your Terminal and execute the following to create a new Symfony-Project\\nYou need the first line only if you used the PHP Project type for your workspace.

\\n
    rm README.md php.ini hello-world.php\\n    composer create-project symfony/framework-standard-edition symfony/ \\\"2.5.*\\\"\\n    mv symfony/{*,.*} ./ \\n    rm -rf symfony
\\n

The create-project composer command will ask for a few parameters, the only one you need to pay special attention is the database-host parameter.

\\n

Running the project

\\n

There is a IP address checking in the web/app_dev.php file. To disable this check please remove the following lines

\\n
    // This check prevents access to debug front controllers that are deployed by accident to production servers.\\n    // Feel free to remove this, extend it, or make something more sophisticated.\\n    if (isset($_SERVER['HTTP_CLIENT_IP'])\\n        || isset($_SERVER['HTTP_X_FORWARDED_FOR'])\\n        || !in_array(@$_SERVER['REMOTE_ADDR'], array('127.0.0.1', 'fe80::1', '::1'))\\n    ) {\\n        header('HTTP/1.0 403 Forbidden');\\n        exit('You are not allowed to access this file. Check '.basename(__FILE__).' for more information.');\\n    }
\\n

After that add a new run configuration in Menu Run > Run Configurations > New Run Configuration. Select Apache http (PHP, HTML) as a Runner and web/app_dev.php as Command.\\nThat's it after you hit Run your server will start up and you can access your new Symfony project.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"create_a_workspace\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Create a Workspace\",\n \"contents\": \"\\n

Create a Workspace

\\n

Cloud9 supports three types of workspaces:

\\n
    \\n
  1. Hosted
    2. \\n
  2. FTP
    3. \\n
  3. SSH
    4. \\n
\\n

"Hosted" is the best choice for most people, so in this short "Getting Started" article we'll only describe this option; for other options please read the full Creating a new workspace article.

\\n

The first step for creating a new workspace is click the "CREATE NEW WORKSPACE" button in your Dashboard:

\\n

\\\"New

\\n

At this point, you'll encounter two choices: Create a new workspace and Clone from URL. \\nIn this article we'll only describe the Create a New Workspace option, which allows you to create any of the previously mentioned types of workspaces (hosted, FTP, or SSH).

\\n

After clicking on Create a new workspace, you're taken to the screen below:

\\n

\\\"Options

\\n

First, let's enter a workspace name.\\nDepending on whether you have a Free of Premium account, you can choose to make it either Public (open to anyone with the URL), or Private (only accessible to you and people you share it with).

\\n

After this, choose the type of workspace you want to create:

\\n\\n

Choose the "Hosted" workspace type to start from scratch with a 'Custom' workspace, or simply pick a pre-configured environment like Node.js, WordPress, or Python/Django, and immediately start developing your app.\\nThis way you don't need to spend valuable development time on system setup and maintenance, as we maintain it, and you control it.

\\n

\\\"Options

\\n

As it's powered by a full Linux Ubuntu environment, hosted workspaces allow you to install any package (sudo apt-get install package), run git commands from the console to push your changes to a GitHub repo or a Bitbucket git repo, etcetera.

\\n

Now press Create. That's it! You can now see your new workspace in the dashboard:

\\n

\\\"New

\\n

Now, just click Start Editing to get started!

\\n

Next up, read how to run an application and set up a database.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"run_an_application\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Run an application\",\n \"contents\": \"\\n
\\n

Run an application

\\n

On Hosted and SSH workspaces, Cloud9 provides two ways to run your application:

\\n
    \\n
  1. Using the Run panel with built-in Runners for many languages
    2. \\n
  2. From a Terminal
    3. \\n
\\n

Method 1: Use the Run panel

\\n

First, open the file you want to run.

\\n

Next, click on the Run button in the top menu bar in the IDE.

\\n

\\\"Run

\\n

The Run button acts as a sort of shortcut to the Run panel, which will appear by default in the bottom of the IDE when you run a file.\\nThis automatically runs the currently active file, and it will guess which Runner to use based on the extension of the file.

\\n

When you're ready to stop your app, click on the Stop Button button in the menu bar at any time, or from the Run panel below.

\\n

\\\"Run

\\n

On the Run panel, you'll notice a few more options you can set. \\nFilling these textboxes out creates a Run Configuration.

\\n
    \\n
  • Name: the name of your run scenario
    • \\n
  • Command: the command you want to run; this is usually the location of your running file in your project, but it also allows you to provide any additional command line arguments you want to pass to your app
    • \\n
  • Runner: defines how you want your code to be run. A wide range of Runners is available by default, from Apache to Node.js and Shell scripts, and you can define your own.
    • \\n
  • CWD: Set the current working directory to start from
    • \\n
  • Environment: Set environment variables
    • \\n
  • \\n
\\n

Tip:

If you can't find the Runner you need from the default set, you can create your own custom Runner.\\n\\n
\\n

For some default runners like Node.js, it's an option to Run in debug mode, which indicates that you want to run the current code through the debugger. \\nThis will reveal (or collapse) the debugging tools panel described in Running and Debugging your code.

\\n

Method 2: From the Terminal

\\n

The built-in Terminal provides access to all underlying system commands, including your Runners such as Node.js. \\nSimply open up a Terminal from the "+" sign, or use CMD+T (Mac) / Control+T (Windows), and then execute the command you need to run your app, e.g. node server.js.

\\n

(Pre-)View your application

\\n

To find out where your application is running you can do two things:

\\n
    \\n
  1. Use the Preview button on the top to preview one of your files. The URL in the browser bar in the Preview can also be used in any browser tab/window.
    2. \\n
  2. Use the Share button on the top to figure out the URLs of running Application and the Preview. The Editor URL is only used to share your entire Cloud9 workspace to collaborate on code.
    3. \\n
\\n

Tip:

If you can't find how to preview your running app, try to use port 8080 in the URL.
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setup_a_database\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Set up a database\",\n \"contents\": \"\\n
\\n

Set up a database

\\n

MySQL

\\n

From the Terminal, run the following command:

\\n
$ mysql-ctl install
\\n

The output will be:

\\n
MySQL 5.5 database added.  Please make note of these credentials:\\n\\nRoot User: username\\nDatabase Name: c9
\\n

Now you can connect to the database using the ip 127.0.0.1 and the default port 3306.\\nYou can also test it using our tool from the Terminal:

\\n
$ mysql-ctl cli\\nWelcome to the MySQL monitor.  Commands end with ; or \\\\g.\\nYour MySQL connection id is 24\\nServer version: 5.5.37-0ubuntu0.14.04.1 (Ubuntu)\\n\\nCopyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved.\\n\\nOracle is a registered trademark of Oracle Corporation and/or its\\naffiliates. Other names may be trademarks of their respective\\nowners.\\n\\nType 'help;' or '\\\\h' for help. Type '\\\\c' to clear the current input statement.\\n\\nmysql>  show databases;\\n+--------------------+\\n| Database           |\\n+--------------------+\\n| information_schema |\\n| c9                 |\\n| mysql              |\\n| performance_schema |\\n+--------------------+\\n4 rows in set (0.15 sec)
\\n

MongoDB

\\n

From the Terminal, run the following command:

\\n
$ mongod --bind_ip=$IP --nojournal
\\n

The output will include:

\\n
...\\nwaiting for connections on port 27017
\\n

Now you can open the mongo shell in a new Terminal, running following command:

\\n
$ mongo
\\n

To stop the MongoDB instance press Control+C in the Terminal where mongod is running.\\nNow have a look at the currently used database:

\\n
$ mongo\\nmongo> db\\ntest
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"share_a_workspace\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Share a workspace\",\n \"contents\": \"\\n
\\n

Share a workspace

\\n

As you develop your application, often you just want to quickly demo your work-in-progress to a colleague, customer, or friend. \\nOr you want to pull in a fellow dev to debug an issue, or to pair program.

\\n

Cloud9 enables you to do just these things, easily: share your entire development environment, the running application, or just a preview of your running application. \\nHere we describe how to access these options, and how to use each.

\\n

Share dialog

\\n

The best place to start sharing is from the dedicated "Share" dialog. \\nAccess it via the "Share" button on the right top of the IDE, or via the menu in Window > Share...

\\n

\\\"Share

\\n

Here's what you see when you pull up the Share dialog:

\\n

\\\"Share

\\n

Links to share

\\n
    \\n
  • Editor: see section "Share your development environment"
    • \\n
  • Application: see section "Share your application"
    • \\n
  • \\n
\\n

If you enable the "Public" checkbox for an option, it will make the URL accessible for anyone with the URL.\\nFor public workspaces all these URLs are public by default, but for private workspaces you have to enable them manually.

\\n

Who has access

\\n

This section refers to people you have specifically granted access to your entire development environment.\\n(R) gives Read access only to that person: the ability to open and view files, and to run your code.\\n(RW) or "Read/Write" also gives that person the ability to write to files.

\\n

Invite people

\\n

This section enables you to invite people to your workspace and immediately set if they have just "Read" or "Read+Write" rights. \\nYou can invite people by their email address or Cloud9 username. \\nYou can also choose whether or not send an automatic email to that person that they've been invited to your workspace.

\\n

Share your development environment

\\n

Cloud9's Collaboration features allow you to share your entire development environment so you can work on code together, much like working on a document in Google Docs.\\nYou'll actually be able to see each other's cursor as you type, run your app, share the Terminal(s), and talk in the group chat.\\nSee the screenshot below for what this looks like:

\\n

\\\"Collaboration

\\n

In order to share your entire development environment, do one of the following:

\\n
    \\n
  1. Make the URL publicly available to everyone: check the "Public" checkbox for the "Editor" in the "Links to Share" section.
    2. \\n
  2. Choose to share only with specific people: invite them from the "Invite people" section.
    3. \\n
  3. Grant/revoke access rights in the "Who has access" section.
    4. \\n
\\n

If someone asks for either Read or Read+Write access to your workspace, you can accept or deny them from the Collaboration panel on the right.

\\n

Note:

alternatively you can just share the URL to your workspace from the browser's URL bar and accept members as they request access to your workspace\\n\\n
\\n

Share your application

\\n

If you Run your application the result can be shared by copying the URL from the dialog. \\nThis URL can only be viewed if it's made Public by checking the "Public" checkbox next to the "Application" in the "Links to share" section.

\\n

People who have full read access to your workspace (as defined in the "Who has access") can view this URL whether it's public or not.

\\n

Note:

alternatively you can just share the URL to your running app from the Preview panels' URL bar\\n\\n
\\n

Share a Preview

\\n

If you Preview a file in your application, it can be shared by copying the URL from the dialog. \\nThis URL can only be viewed if it's made Public by checking the "Public" checkbox next to the "Preview" in the "Links to share" section.

\\n

People who have full read access to your workspace (as defined in the "Who has access") can view this URL whether it's public or not.

\\n

Note:

alternatively you can just share the URL to your Preview from the Preview panels' URL bar\\n\\n
\\n

Tip:

If you can't find how to preview your running app, try to use port 8080 in the URL.
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"console\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"The Console\",\n \"contents\": \"\\n
\\n

The Console

\\n

Note:

this feature is deprecated\\n\\n
\\n

The Console is at the bottom of the IDE. It's where you can enter command line input, view output from your program, and push and pull your files between your code repositories.

\\n

Note:

The Console contains a full-fledged terminal, which provides you with a TTY interface for direct access to the machine that Cloud9 is running on.\\n\\n
\\n

Available Commands

\\n

The terminal can perform all Unix commands, and allows for path autocompletion by hitting Tab.

\\n

For instance, you can use mercurial commands (hg) and git commands (git) to communicate with the system, and to push your code between repositories. Typing hg or git shows the complete list of commands that are available for these services. For more information about these commands, please check their respective documentation:

\\n\\n

To use mercurial commands on the project you are working on, you must have a mercurial project set up; the same holds true for git. Follow these links to learn more about how to set up these project in Cloud9:

\\n\\n

Output

\\n

The output tab in the Console shows information whenever a user is running or debugging a program. The content is similar to the output of a desktop terminal:
\\\"Screenshot

\\n

The output tab also displays the error and additional information that can improve your coding quality. You can use the Console to output results from your running application, just like a regular terminal.

\\n

As your process runs, you'll see a message similar to this one indicating that Cloud9 is running something in the background: \\\"Running

\\n

If you hover over this message, you can opt to cancel the process by clicking on the button: \\\"Cancelling

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"dashboard\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"The Dashboard\",\n \"contents\": \"\\n

The Dashboard

\\n

After you have logged into Cloud9, you are placed into your account's dashboard. From here, you can edit your profile and manage workspaces you have access to.

\\n

\\\"An

\\n

In the top-left corner of the dashboard, your username is displayed. Within the user context, you can view your user profile by clicking on Your Account:

\\n

\\\"A

\\n

The user profile contains:

\\n
    \\n
  • Your recent activities, including a list of actions you have recently performed, such as cloning, opening, and deleting projects
    • \\n
  • Your add-on services, which you've integrated into Cloud9. Currently, these are GitHub and Bitbucket.
    • \\n
  • Your account settings, where you're given the following choices:
      \\n
    • Change your password
      • \\n
    • Show your SSH key
      • \\n
    • Upgrade to premium (or, downgrade from it)
      • \\n
    • Delete your account
      • \\n
    \\n
    • \\n
\\n

The gravatar that is used for your profile is handled by gravatar.com. If you don't have a gravatar yet, Cloud9 IDE uses an uninspiring default.

\\n

In the left panel, you'll find a list of various projects associated with your account. These are:

\\n
    \\n
  • My Projects: these are projects you've created or cloned, and own
    • \\n
  • Shared With Me: these are projects shared with you by other Cloud9 users
    • \\n
  • Recently Visited: these are projects you've seen lately
    • \\n
  • Projects on GitHub: a list of your uncloned public and private GitHub projects
    • \\n
  • Projects on Bitbucket: a list of your uncloned public and private Bitbucket projects
    • \\n
\\n

Clicking on the \\\"Project next to MY PROJECTS lets you:

\\n
    \\n
  • Create a new project
    • \\n
  • Clone from URL
    • \\n
\\n

\\\"Creating

\\n

For more information on creating new workspaces, see this section of the documentation.

\\n

You can always filter your project list by entering text in the text bar to find matching projects. If you need to update the list, click the refresh icon at the bottom of the panel: \\\"Refresh

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"ide_overview\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"IDE Overview\",\n \"contents\": \"\\n
\\n

IDE Overview

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n

Cloud9 IDE can be thought of as being divided into the following components:

\\n

\\\"IDE

\\n

Throughout the documentation, we'll refer to these sections by name. We can identify several distinct areas in the editor:

\\n
    \\n
  • The top menu bar is the uppermost area, with easy access to a variety of menus
    • \\n
  • The project bar on the left lets you manipulate various aspects of your project, including its active files, preferences, and choices for deployment
    • \\n
  • The panel displays views according to what's been selected in the project bar
    • \\n
  • The toolbar is on the far right, where you can find tools used when debugging your code. Projects that are open with collaboration also make use of this panel for chatting.
    • \\n
  • The code editor is the main area where you write your code.
    • \\n
  • The console is the bottom area of the window. It's an expandable area that can act like a desktop terminal to enter command line input (like ls or mkdir). It also displays output provided by your program's print statements (like console.log()), as well as providing an area for search results
    • \\n
\\n

The Project Bar, Tool Bar, and Console are powerful features, so their documentation is provided separately. We'll talk about the rest of the editor below:

\\n

Remember: nearly every UI element can be collapsed, in order to provided a more harmonious coding experience. For example, clicking on the buttons in the upper left of the editor allows you to hide the panels and top menu bar:
\\\"Hiding

\\n

The Top Menu Bar

\\n

\\\"A

\\n

In this section, you can find the usual menus for creating and saving files, changing your view, applying a new theme for the editor, and switching between windows.

\\n

In the middle of the menu bar you'll find the debug button: \\\"The. This is used for running and debugging your code. For more information, see the section on "Running and Debugging Your Code"..

\\n

\\n

The preview button \\\"The provides you with a look of what the currently active file would look like in the browser. For text files, this is usually just the raw text, but certain files, like HTML or XML, render as the actual markup.

\\n

The autosave button indicates the status of your current saves: \\\"Autosave. Files are saved automatically by Cloud9 IDE, and every revision is made available for you to browse through. For more information, see the section on revisions and saving.

\\n

On the far right of the menu, near the Cloud9 IDE logo, there are two more icons: one to return to the dashboard, and one to return to the Cloud9 IDE homepage.

\\n

The Code Editor

\\n

This is where most of the action happens. Every file you open appears here as a tab. You can open a new file easily by clicking on the \\\"Tab button to the right of the last tab. Cloud9 IDE offers syntax highlighting for over two dozen programming languages.

\\n

The code editor supports a large number of keyboard shortcuts to increase your productivity. For an up-to-date list of these within the IDE, simply go to Help > Keyboard Shortcuts.

\\n

If you hover over to the upper-right corner, you can activate zen-mode, which is a full screen coding environment.

\\n

At the lower-right corner, you can find the status bar.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"ide_preferences\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"IDE Preferences\",\n \"contents\": \"\\n
\\n

IDE Preferences

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n

There are many different ways to configure the IDE. Below is a list of the options available, and what they do.

\\n

Note:

All of these options are on a per-project basis. Changing them in one project does not affect any another.\\n\\n
\\n

General

\\n

This section controls the overall IDE behavior:

\\n\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
Preference NameDescription
Enable UI AnimationsEnables or disables fluid animations for various UI elements, such as the Project Bar
Animate ScrollingEnables or disables fluid animations when scrolling through code (such as for goto line)
Enable Auto-SaveIf enabled, automatically saves your files on every change
On Save, Strip WhitespaceWhen saving a file, you can remove all extraneous whitespace from your code lines
Reveal Active File in Project TreeEnabling this jumps the project tree to the active file whenever a tab changes to a different file
Warn Before ExitingPrevents accidental data loss by showing a dialog asking if you really want to leave Cloud9 IDE when closing your browser
Node.js RuntimeDefines the default runtime for your Node.js code. "Auto" is based on whatever is in the package.json file, while "Default" reverts to Node 0.6.x.
KeybindingsAllows you to choose which operating system to use for keyboard shortcuts
\\n

Language Support

\\n

This section controls language analysis options:

\\n\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
\\n \\n \\n \\n \\n \\n \\n \\n
Preference NameDescription
Enable Hints and Warnings RulesPresents information about your code in the gutter
Highlight Variable InstancesHighlights variable instances in your code
Mark Undeclared VariablesProvides warnings if a variable is being used and has not been declared yet
Mark Unused Function ArgumentsProvides a strikethrough for arguments in a function that are not being used
Warning LevelSpecifies the minimum level of information severity you want provided in the gutter
\\n

Code Editor

\\n

This section controls language analysis options:

\\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
Preference NameDescription
Auto-pair Quotes, Brackets, etc.When enabled, typing ", (, or [ will actually make two characters appear. In addition, whenever you highlight a word and type one of these characters, it is surrounded by that character (e.g. words becomes "words")
Full Line SelectionWhen highlighting lines, this option will highlight all ending whitespace, until the end of the editor window
Highlight Active LinePresents a darker shade in the code editor to indicate which line you're currently on
Highlight Gutter LinePresents a darker shade in the gutter which line you're currently on
Show Invisible CharactersShows invisibles characters in the editor, like tabs and line breaks
Show Indent GuidesShows the indent guides in the editor, letting you see your code's nestings
Show GutterShows the gutter in the editor, which indicates line numbers, warnings, and errors
Highlight Selected WordIf you highlight a word, this highlights all matching words in the editor
Auto-hide Horizontal ScrollWhen this is enabled, this will hide the horizontal scroll bar in the editor. Note that this has no effect in Mac OS X 10.7 (Lion) and above, since all scrollbars, by default, auto-hide.
Vim ModeWhen enabled, allows you to use vim keybindings in the IDE
Code FoldingWhen enabled, allows you to show or hide "blocks" of code
Fade Fold WidgetsWhen enabled, fades the folding widgets in the gutter
Font SizeChanges the font size of the code in the editor
Show Print MarginShows (and defines) the number of characters possible in line, before it wraps
Soft TabsIndicates how many spaces a single tab represents
Mouse Scroll SpeedDefines the speed of the mouse scrolls
Newline ModeSpecifies the newline mode for the IDE
\\n

Terminal

\\n

This section controls the behavior for the terminal:

\\n
\\n \\n \\n \\n \\n \\n \\n \\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
\\n \\n \\n \\n
Preference NameDescription
ScrollbackSets the scrollback buffer for the terminal
Font FamilySets the font for the terminal
Font SizeSets the font size for the terminal
Blinking CursorSpecifies whether or not you want the cursor to blink
\\n

Code Tools

\\n

This section controls the various tools that are available in the IDE:

\\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n\\n \\n \\n
Preference NameDescription
Enable Color PickerMakes the color picker available for use
Preserve Empty LinesWhen enabled, the editor keeps any new lines without text
Keep Array IndentionWhen enabled, tabs and newlines in arrays are preserved. For example, the follow array would remain as-is with this option:\\n 
\\n        var o = [{\\n            a: b\\n        }, {\\n            c: d\\n        }];\\n
\\n
JSLint Strict WhitespaceIf selected, all brackets are preceded by a space. For example, if(x){ becomes if (x) {, and function(arg){ becomes function (arg) {
BracesThese options control how braces are handled in the IDE:\\n
    \\n
  • Braces with control statement: braces are left "in-line" alongside the code statements. For example, code is formatted like this:\\n 
    \\n    if (true) {\\n        var x = 3;\\n    } else {\\n        var x = 5;\\n    }\\n
    \\n
    • \\n
  • Braces on own line: braces are always placed on their own line. For example, code is formatted like this:\\n 
    \\n    if (true)\\n    {\\n        var x = 3;\\n    } else\\n    {\\n        var x = 5;\\n    }\\n
    \\n
    • \\n
  • End braces on own line: only the ending braces have their own line. For example, code is formatted like this:\\n 
    \\n    if (true) {\\n        var x = 3;\\n    }\\n    else {\\n        var x = 5;\\n    }\\n
    \\n
    • \\n
\\n
\\n
\\n
\\n \"\n },\n {\n \"filename\": \"keybindings\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Commands and Keybindings\",\n \"contents\": \"\\n

Commands and Keybindings

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n

Nearly every action in Cloud9 has a corresponding command associated with it. On top of that, every command also has a keybinding that can be used to effortlessly execute the command.

\\n

Below is a list of every single command and keybinding used by Cloud9. Have fun being efficient!

\\n
\\n \\n
\\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
Command NameKeybinding
Abortclicommand˄-C
AddCursorAbove˄-⌥-Up
AddCursorAboveSkipCurrent˄-⌥-⇧-Up
AddCursorBelow˄-⌥-Down
AddCursorBelowSkipCurrent˄-⌥-⇧-Down
Backspace˄-⌫
Beautify⌘-⇧-B
Clearcut⎋
Closeallbutme⌥-˄-W
Closealltabs⌥-⇧-W
Closetab⌥-W
Complete˄-Space
Copy⌘-C
Copylinesdown⌘-⌥-Down
Copylinesup⌘-⌥-Up
Cut⌘-X
DelDelete
DuplicateSelection⌘-⇧-D
Escapeconsole⎋
EvalInteractive⌘-Return
Find⌘-F
Findnext⌘-G
Findprevious⌘-⇧-G
Fold⌘-⌥-L
Foldall⌘-⌥-0
GolinedownDown
GolineupUp
Gotoend⌘-End
Gotofile⌘-E
GotoleftLeft
Gotoline⌘-L
Gotolineend⌘-Right
Gotolinestart⌘-Left
GotopagedownPageDown
GotorightRight
Gotostart⌘-Home
Gototableft⌘-[
Gototabright⌘-]
Gotowordleft⌥-Left
Gotowordright⌥-Right
IndentTab
Jumptomatching˄-⇧-P
Largerfont˄-⇧-.
Movelinesdown⌥-Down
Movelinesup⌥-Up
Movetableft⌘-⌥-[
Movetabright⌘-⌥-]
Newfile⌥-⇧-N
Newfiletemplate⌥-˄-N
Newfolder⌥-˄-⇧-N
Nexttab⌥-Tab
Openfilepanel⇧-⌘-U
Opensettingspanel⌘-,
Opentreepanel⌘-U
Outdent⇧-Tab
Outline⌘-⇧-E
Paste⌘-V
Previoustab⌥-⇧-Tab
Quicksave⌘-S
Quickwatch⌥-Q
Redo⌘-⇧-Z
Removeline⌘-D
Removetolineend˄-K
Removetolinestart⌘-⌫
Removewordleft⌥-⌫
Removewordright⌥-Delete
RenameVar⌥-⌘-R
Replace⌥-⌘-F
Replaymacro⌘-˄-R
ResumeF8
Revealtab⇧-⌘-L
Reverttosaved˄-⇧-Q
Revisionpanel⌘-B
RunF5
Saveas⌘-⇧-S
Savetabsession⇧-˄-S
Searchinfiles⇧-⌘-F
SelectMoreAfter˄-⌥-Right
SelectMoreBefore˄-⌥-Left
SelectNextAfter˄-⌥-⇧-Right
SelectNextBefore˄-⌥-⇧-Left
Selectall⌘-A
Selectdown⇧-Down
Selectleft⇧-Left
Selectright⇧-Right
Selecttoend⌘-⇧-Down
Selecttolineend⌘-⇧-Right
Selecttolinestart⌘-⇧-Left
Selecttostart⌘-⇧-Up
Selectup⇧-Up
Selectwordleft⌥-⇧-Left
Selectwordright⌥-⇧-Right
Smallerfont˄-⇧-,
SplitIntoLines˄-⇧-L
StepintoF11
Stepout⇧-F11
StepoverF10
Stop⇧-F5
Switchconsole⇧-⎋
Tab0⌘-0
Tab1⌘-1
Tab2⌘-2
Tab3⌘-3
Tab4⌘-4
Tab5⌘-5
Tab6⌘-6
Tab7⌘-7
Tab8⌘-8
Tab9⌘-9
ToggleTabs˄-M
Togglecomment⌘-/
Toggleconsole˄-⎋
Togglerecording⌘-⇧-R
Tolowercase˄-⇧-U
Touppercase˄-U
Transposeletters˄-T
Undo⌘-Z
Unfold⌘-⌥-⇧-L
Unfoldall⌘-⌥-⇧-0
Zen⌥-Z
Zenslow⇧-⌥-Z
\\n
\\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
Command NameKeybinding
AbortclicommandCtrl-C
AddCursorAboveCtrl-Alt-Up
AddCursorAboveSkipCurrentCtrl-Alt-Shift-Up
AddCursorBelowCtrl-Alt-Down
AddCursorBelowSkipCurrentCtrl-Alt-Shift-Down
BackspaceCommand-Backspace
BeautifyShift-Ctrl-B
ClearcutESC
CloseallbutmeCtrl-Alt-W
ClosealltabsCtrl-Shift-W
ClosetabCtrl-W
CompleteCtrl-Space
CopyCtrl-C
CopylinesdownAlt-Shift-Down
CopylinesupAlt-Shift-Up
CutCtrl-X
DelDelete
DuplicateSelectionCtrl-Shift-D
EscapeconsoleEsc
EvalInteractiveCtrl-Return
FindCtrl-F
FindnextCtrl-K
FindpreviousCtrl-Shift-K
FoldAlt-L
FoldallAlt-0
GolinedownDown
GolineupUp
GotoendCtrl-End
GotofileCtrl-E
GotoleftLeft
GotolineCtrl-G
GotolineendAlt-Right
GotolinestartAlt-Left
GotopagedownPageDown
GotorightRight
GotostartCtrl-Home
GototableftCtrl-[
GototabrightCtrl-]
GotowordleftCtrl-Left
GotowordrightCtrl-Right
IndentTab
JumptomatchingCtrl-P
LargerfontCtrl-Shift-.
MovelinesdownAlt-Down
MovelinesupAlt-Up
MovetableftCtrl-Alt[
MovetabrightCtrl-Alt-]
NewfileCtrl-N
NewfiletemplateCtrl-Alt-N
NewfolderCtrl-N
NexttabCtrl-Tab
OpenfilepanelShift-Ctrl-U
OpensettingspanelCtrl-,
OpentreepanelCtrl-U
OutdentShift-Tab
OutlineCtrl-Shift-E
PasteCtrl-V
PrevioustabCtrl-Shift-Tab
QuicksaveCtrl-S
QuickwatchAlt-Q
RedoCtrl-Shift-Z
RemovelineCtrl-D
RemovetolineendAlt-Delete
RemovetolinestartAlt-Backspace
RemovewordleftCtrl-Backspace
RemovewordrightCtrl-Delete
RenameVarCtrl-Alt-R
ReplaceAlt-Shift-F
ReplaymacroAlt-R
ResumeF8
RevealtabCtrl-Shift-L
ReverttosavedCtrl-Shift-Q
RevisionpanelCtrl-B
RunF5
SaveasCtrl-Shift-S
SavetabsessionShift-Ctrl-S
SearchinfilesCtrl-Shift-F
SelectMoreAfterCtrl-Alt-Right
SelectMoreBeforeCtrl-Alt-Left
SelectNextAfterCtrl-Alt-Shift-Right
SelectNextBeforeCtrl-Alt-Shift-Left
SelectallCtrl-A
SelectdownShift-Down
SelectleftShift-Left
SelectrightShift-Right
SelecttoendCtrl-Shift-End
SelecttolineendAlt-Shift-Right
SelecttolinestartAlt-Shift-Left
SelecttostartCtrl-Shift-Home
SelectupShift-Up
SelectwordleftCtrl-Shift-Left
SelectwordrightCtrl-Shift-Right
SmallerfontCtrl-Shift-,
SplitIntoLinesCtrl-Shift-L
StepintoF11
StepoutShift-F11
StepoverF10
StopShift-F5
SwitchconsoleShift-Esc
Tab0Ctrl-0
Tab1Ctrl-1
Tab2Ctrl-2
Tab3Ctrl-3
Tab4Ctrl-4
Tab5Ctrl-5
Tab6Ctrl-6
Tab7Ctrl-7
Tab8Ctrl-8
Tab9Ctrl-9
ToggleTabsCtrl-M
TogglecommentCtrl-/
ToggleconsoleF6
TogglerecordingAlt-Shift-R
TolowercaseCtrl-Shift-U
TouppercaseCtrl-U
TransposelettersCtrl-T
UndoCtrl-Z
UnfoldAlt-Shift-L
UnfoldallAlt-Shift-0
ZenAlt-Z
ZenslowShift-Alt-Z
\\n
\\n
\\n
\\n
\\n
\\n \"\n },\n {\n \"filename\": \"project_bar\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"The Project Bar\",\n \"contents\": \"\\n

The Project Bar

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n

The project bar is located towards the left of the Cloud9 IDE: \\\"The

\\n

The buttons in the project bar allow you to reveal and hide panels for the IDE. In more detail:

\\n
    \\n
  • Pressing on the Cloud9 icon collapses the panel area
    • \\n
  • Project Files shows your workspace's directory structure. You can view all your files here. Right-clicking within this panel reveals a drop-down menu with additional options, such as the ability to rename files or create new directories.
    • \\n
  • Active Files lists your files that are currently open.
    • \\n
  • Run & Debug lets you run and debug your code live, in the browser. For more information, see the section on "Running and Debugging Your Code".
    • \\n
  • Deploy allows you to deploy to a variety of services. For more information, see the section on "Deploying Your Code".
    • \\n
  • Preferences lets you change the behavior of the editor. The Preferences documentation is provided on its own page.
    • \\n
\\n

Clicking on any button expands its menu. Clicking on an expanded menu causes it to collapse, which gives you more room in the IDE to work with.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"status_bar\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Status Bar\",\n \"contents\": \"\\n

Status Bar

\\n

Note:

this feature is deprecated\\n\\n
\\n

The status bar is designed to provide you with all sorts of information about your code--and additional functionality--without getting in the way of the IDE. It's quite tiny, and quite powerful, like a weight-lifting squirrel.

\\n

You can find the status bar in the lower-right corner of the editor: \\\"The. Keep in mind that the status bar is transparent, so it's able to camoflauge well with light or dark themes.

\\n

There's three pieces of crucial information available at all times: your current row, your current column, and, if you're highlighting characters, the status bar displays the number of bytes currently selected. If you're using Vim Mode, the status bar also tells you if you're in INSERT mode.

\\n

If you click on the status bar, it expands into a menu that provides a smaller set of the full IDE preferences. These options only deal with the IDE editor:

\\n
\\n \\n \\n \\n \\n \\n \\n \\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
Preference NameDescription
Show InvisiblesShows invisibles characters in the editor, like tabs and line breaks
Wraps LinesWraps lines according to the line margin defined, or your browser's window. Otherwise, lines run off the current viewport.
Code FoldingWhen enabled, allows you to show or hide "blocks" of code
Full Line SelectionWhen highlighting lines, this option will highlight all ending whitespace, until the end of the editor window
Highlight Active LinePresents a darker shade in the code editor to indicate which line you're currently on
Show Indent GuidesShows the indent guides in the editor, letting you see your code's nestings
Show GutterShows the gutter in the editor, which indicates line numbers, warnings, and errors
Highlight Selected WordIf you highlight a word, this highlights all matching words in the editor
Auto-pair Quotes, Brackets, etc.When enabled, typing ", (, or [ will actually make two characters appear. In addition, whenever you highlight a word and type one of these characters, it is surrounded by that character (e.g. words becomes "words")
Auto-hide Horizontal Scrollbarhen this is enabled, this will hide the horizontal scroll bar in the editor. Note that this has no effect in Mac OS X 10.7 (Lion) and above, since all scrollbars, by default, auto-hide.
Font SizeChanges the font size of the code in the editor
Show Print MarginShows (and defines) the number of characters possible in line, before it wraps
Soft TabsIndicates how many spaces a single tab represents
Mouse Scroll SpeedDefines the speed of the mouse scrolls
\\n
\\n
\\n
\\n \"\n },\n {\n \"filename\": \"terminal\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Terminal\",\n \"contents\": \"\\n

Terminal

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n

The terminal provides you with a TTY interface for direct access to the machine that Cloud9 is running on. If you're running your own workspace, this is the server you've SSH'ed into. If you're using the hosted Cloud9 platform, this is the server your code runs on.

\\n

Warning:

While certain operations, like sudo, are restricted, you can completely destroy your workspace, by doing something like rm -rf. Use your power wisely!\\n\\n
\\n

To create a new terminal, go to View > Terminals > New Terminal, or simply type Alt-T on the keyboard. The terminal has the following capabilities:

\\n
    \\n
  • Perform all Unix commands
    • \\n
  • You can create more than one instance of a terminal (by just creating a new tab)
    • \\n
  • The terminal allows for path autocompletion by hitting Tab
    • \\n
\\n

\\\"Screenshot

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"tab_functions\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Tab Functions\",\n \"contents\": \"\\n
\\n

Tab Functions

\\n

Note:

this article is outdated, a new version will follow soon\\n\\n
\\n

Cloud9 IDE offers advanced tab features to make working with multiple files easy. By right-clicking on any tab, you'll open up the tab context menu:

\\n

\\\"The

\\n

These feature include:

\\n
    \\n
  • Reveal in File Tree: opens the current file in the Project Files tree
    • \\n
  • Close Tab: closes the current tab
    • \\n
  • Close All Tabs: closes all the opened files
    • \\n
  • Close All But Current Tab: closes all the opened files, except the current one
    • \\n
  • Close Tabs to the Right/Left: closes all opened tabs to the right (or left) of the current one
    • \\n
  • File Revision History...: launches the revisions panel
    • \\n
\\n

To the left of the tab menu is another button that offers additional functions for tab navigation:
\\\"The

\\n

Tab Sessions

\\n
\\n\\n
\\n\\n

Tab sessions is a unique feature that is useful when dealing with projects that involve juggling between many tabs. Essentially, tab sessions lets you save the current state of the tabs. You can close your workspace, switch to a different branch, and instantly reload your previously opened files. You'll no longer need to work with opening and closing multiple files.

\\n

To use tab sessions, select Save Tab Sessions from the tab button menu. Give it a unique name. When you're ready to restore your tab sessions, just select Load Tab Sessions.

\\n

If you find that you've got too many tab sessions defined, you can always choose to delete them from the same tab menu.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"the_editor\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"The Editor\",\n \"contents\": \"\\n

The Editor

\\n

The editor is the most important element of any IDE; that's why Cloud9 developed ACE. ACE is a high-performance code editor for the web that supports over 40 different languages, over two dozen themes, and can still work faithfully on large documents (at last count, four million lines of code was the upper limit). It also contains a bevy of features you'd expect from traditional desktop editors. Among these include:

\\n
    \\n
  • Undo and Redo support
    • \\n
  • Cut, Copy, and Paste functionality
    • \\n
  • Line manipulation, including:
      \\n
    • Indenting and outdenting
      • \\n
    • Moving and copying lines up or down
      • \\n
    • Removing lines from any point
      • \\n
    • Splitting lines
      • \\n
    \\n
    • \\n
  • Highlighting and commenting blocks of code
    • \\n
  • Removing words to the right or the left
    • \\n
  • Transposing letters
    • \\n
  • Code folding (including the entire file)
    • \\n
  • Converting cases
    • \\n
  • Multiple cursors
    • \\n
  • Autocompletion
    • \\n
  • Code analysis and refactoring
    • \\n
  • Search in files with regular expressions
    • \\n
  • Intelligent selections, including:
      \\n
    • Selecting to word right or left
      • \\n
    • Selecting to line end or start
      • \\n
    • Selecting to document end or start
      • \\n
    \\n
    • \\n
  • Vim and Emacs keybindings
    • \\n
  • Line wrapping, to a defined column or the width of the browser window
    • \\n
  • Support for a command line
    • \\n
  • Support for spaces and real tabs
    • \\n
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"index\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Cloud9 IDE User Documentation\",\n \"contents\": \"\\n

Welcome to the official Cloud9 IDE documentation! Here, you'll find articles and tutorials to help you use the Cloud9 platform. These include everything from setting up a workspace, to learning how to run, debug, and deploy your code.

\\n\\n\\n

Getting started

\\n

Have a look at the "Getting Started" section on the left for an introduction into the basics of Cloud9.\\nFor instance, read up on how to:

\\n\\n

Getting More Help

\\n

If you're interested in troubleshooting specific aspects of the IDE, need help setting up an account, or just want to chat with our support team, please visit the Support pages.

\\n

Contact Us

\\n

Remember: All of our documentation content is open-sourced on GitHub, just like our amazing IDE.

\\n

See something that's not documented here? Simply add it to the documentation with a Pull Request, or send an e-mail to docs@c9.io, and we'll get it in.

\\n

Recently Updated Topics

\\n

Here's a list of the last five recently updated topics:

\\n\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_hosted_mysql\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"MySQL\",\n \"contents\": \"\\n
\\n

MySQL

\\n

MySQL is the world's most widely used open source relational database management system (RDBMS) that runs as a server providing multi-user access to a number of databases.

\\n

MySQL's most common features

\\n
    \\n
  • A broad subset of ANSI SQL 99, as well as extensions
    • \\n
  • Cross-platform support
    • \\n
  • Stored procedures
    • \\n
  • Triggers
    • \\n
  • Cursors
    • \\n
  • Updatable Views
    • \\n
  • Information schema
    • \\n
  • Many more
    • \\n
\\n

Using MySQL with Cloud9

\\n

Cloud9 IDE does not support installing a MySQL database (yet). As a workaround you can choose to connect your project to a MySQL database hosted elsewhere. Xeround\\noffers hosted MySQL instances and have a free tier available for getting started.

\\n

Xeround

\\n
    \\n
  1. Register with Xeround
    2. \\n
  2. Log in to your controlpanel
    3. \\n
  3. Choose 'create new'
    4. \\n
  4. Choose a datacenter
    5. \\n
  5. Enter your Database name, Username and Password and create
    6. \\n
  6. Select your newly created instance and click the 'External DNS Hostname' link provided to log into PHPMyAdmin
    7. \\n
  7. Create and import/setup your database
    8. \\n
\\n

Cloud9

\\n
    \\n
  1. Log into your account
    2. \\n
  2. Create a new project (or use an existing one)
    3. \\n

  3. Test the connection using the following script:

    \\n
             <?php\\n\\n         $database = new mysqli('instanceNo.db.xeround.com', 'username', 'password', 'databasename', 'port');\\n\\n         if($database->connect_errno > 0){\\n             die ('Database Error' . $database->connect_error); \\n         }else{\\n             die ('Connected!');\\n         }\\n         ?>
    \\n
    4. \\n
  4. Save the file
    5. \\n
  5. Run the file
    6. \\n
\\n

Source

\\n

Courtesy of Roger Qui of Polycadamy. This guide is elaborately explained in a video tutorial

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_mongodb\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"MongoDB\",\n \"contents\": \"\\n
\\n

MongoDB

\\n

MongoDB is a scalable, high-performance, open source NoSQL database.

\\n

MongoDB's most common features

\\n
    \\n

  • Document-Oriented Storage
    \\nJSON-style documents with dynamic schemas offer simplicity and power.

    \\n
    • \\n

  • Full Index Support
    \\nIndex on any attribute, just like you're used to.

    \\n
    • \\n

  • Querying
    \\nRich, document-based queries.

    \\n
    • \\n
\\n

In addition, MongoDB has many scalability features such as:

\\n

Replication, Auto-sharding, Map/Reduce and GridFS

\\n

Running MongoDB on a Cloud9 workspace

\\n

MongoDB is preinstalled in your workspace. To run MongoDB, run the following below (passing the correct parameters to it). Mongodb data will be stored in the folder data.

\\n
$ mkdir data\\n$ echo 'mongod --bind_ip=$IP --dbpath=data --nojournal --rest \\\"$@\\\"' > mongod\\n$ chmod a+x mongod
\\n

You can start mongodb by running the mongod script on your project root:
\\n$ ./mongod

\\n

MongoDB parameters used:

\\n

| Parameter | Description |\\n| ------------------------------ | ----------------------------------------------------------------------------------------------- |\\n| --dbpath=data | Because it defaults to /var/db which isn't accessible) |\\n| --nojournal | Because mongodb usually pre-allocates 2 GB journal file (which exceeds Cloud9 disk space quota) |\\n| --bind_ip=$IP | Because you can't bind to 0.0.0.0) |\\n| --rest | Runs on default port 28017 |

\\n

Drivers

\\n

You should use the host $IP instead of localhost as your driver connection url.
\\ne.g. in Node, it is: process.env.IP

\\n

MongoDB has drivers for all supported runtimes. Following are the most commonly used drivers:

\\n

Node.JS apps

\\n

Mongoose
\\nNode-Mongodb-Native

\\n

Shell Access

\\n

To access a shell prompt for the above MongoDB run the following.

\\n
$ mongo
\\n

Check out docs.mongodb.org for details on how to use the shell

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_mysql\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"MySQL\",\n \"contents\": \"\\n
\\n

MySQL

\\n

MySQL is the world's most widely used open source relational database management system (RDBMS) that runs as a server providing multi-user access to a number of databases.

\\n

MySQL's most common features

\\n
    \\n
  • A broad subset of ANSI SQL 99, as well as extensions
    • \\n
  • Cross-platform support
    • \\n
  • Stored procedures
    • \\n
  • Triggers
    • \\n
  • Cursors
    • \\n
  • Updatable Views
    • \\n
  • Information schema
    • \\n
  • Many more
    • \\n
\\n

Using MySQL with Cloud9

\\n

This article explains our first iteration of MySQL support in Cloud9. It makes it super easy to install, start and stop a MySQL instance right in your workspace. The nice thing is that every workspace will run a separate database so your projects will never interfere with each other. You can control MySQL with the mysql-ctl command line tool run from the terminal:

\\n
# start MySQL. Will create an empty database on first start\\n$ mysql-ctl start\\n\\n# stop MySQL\\n$ mysql-ctl stop\\n\\n# run the MySQL interactive shell\\n$ mysql-ctl cli
\\n

You can then connect to the database with following parameters:

\\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
Option\\n Value\\n Comment\\n
Hostname$IPThe same local IP as the application you run on Cloud9
Port3306The default MySQL port number
User$C9_USERYour Cloud9 user name
Password-No password since you can only access the DB from within the workspace
Databasec9The database name
\\n

Importing data into your database

\\n

To import existing data into your database run following commands:

\\n
mysql-ctl cli
\\n

You are now in the MySQL environment and can start the import:

\\n
mysql> use c9\\nmysql> source PATH_TO_SQL_FILE.sql
\\n

To verify that everything got imported run:

\\n
mysql> show tables;
\\n

Note:

MySQL socket file can be found in ~/lib/mysql/socket/mysql.sock\\n\\n
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_phpmyadmin\",\n \"mtime\": 1416497235000,\n \"pageTitle\": \"PHPMyAdmin\",\n \"contents\": \"\\n
\\n

PHPMyAdmin

\\n

PHPMyAdmin provides an easy to use web interface to manage your MySQL database/s

\\n

PHPMyAdmin's most common features

\\n
    \\n
  • Import data from CSV and SQL
    • \\n
  • Export data to various formats: CSV, SQL, XML, PDF, Word, Excel, LaTeX and others
    • \\n
  • Creating PDF graphics of the database layout
    • \\n
  • Creating complex queries using Query-by-Example (QBE)
    • \\n
  • Searching globally in a database or a subset of it
    • \\n
  • Transforming stored data into any format using a set of predefined functions, like displaying BLOB-data as image or download-link
    • \\n
  • Live charts to monitor MySQL server activity like connections, processes, CPU/Memory usage, etc.
    • \\n
  • Many more
    • \\n
\\n

Using PHPMyAdmin with Cloud9

\\n

This article explains our first iteration of PHPMyAdmin support in Cloud9. It makes it super easy to install a PHPMyAdmin instance right in your workspace. Each workspace runs it's own Database and copy of PHPMyAdmin.

\\n
# Install PHPMyAdmin\\n$ phpmyadmin-ctl install
\\n

After the installation is complete you'll be given a link to access PHPMyAdmin. If you'd like further help using the software please consult the official PHPMyAdmin docs.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_redis\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Redis\",\n \"contents\": \"\\n
\\n

Redis

\\n

Running

\\n

Cloud9 workspaces come with redis pre-installed.

\\n

Start the server:

\\n
sudo service redis-server start
\\n

Connect with the client:

\\n
./redis-cli
\\n

Drivers

\\n

See http://redis.io/clients for drivers.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_postgresql\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"PostgreSQL\",\n \"contents\": \"\\n
\\n

PostgreSQL

\\n

Installing PostgreSQL on a Cloud9 workspace

\\n

PostgreSQL comes preinstalled on every Cloud9 workspace, yay.

\\n

Start the PostgreSQL service

\\n
$ sudo service postgresql start
\\n

Set the "postgres" user password

\\n
$ sudo sudo -u postgres psql                                                                                  \\npsql (9.3.4, server 9.3.5)\\nType \\\"help\\\" for help.\\n\\npostgres=# \\\\password\\nEnter new password: \\nEnter it again: \\npostgres=# \\\\q
\\n

Connect to the service

\\n
$ sudo sudo -u postgres psql
\\n

Create a PostgreSQL database

\\n

Make sure you have logged into the PostgreSQL terminal and then you can just run:

\\n
$ sudo sudo -u postgres psql                                                                                  \\npostgres=# create database \\\"groceries\\\";
\\n

List all databases

\\n
$ sudo sudo -u postgres psql                                                                                  \\npostgres=# \\\\list
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_sqlite3\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"SQLite\",\n \"contents\": \"\\n
\\n

SQLite

\\n

SQLite is a software library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine. SQLite is the most widely deployed SQL database engine in the world. The source code for SQLite is in the public domain.

\\n

Note:

SQLite supports full text search and ACID transactions (atomic, consistent, isolated, and durable)\\nWith its simplicity and zero-configuration, SQLite is a popular choice for new applications.\\n\\n
\\n

Getting started

\\n

You can open the terminal and create a database in a file db_test.db as follows:

\\n

\\\"Screenshot

\\n

Try yourself

\\n
$ sqlite3 db_test.db\\nSQLite version 3.6.20\\nEnter \\\".help\\\" for instructions\\nEnter SQL statements terminated with a \\\";\\\"\\nsqlite> create table tbl1(one varchar(10), two smallint);\\nsqlite> insert into tbl1 values('hello!',10);\\nsqlite> insert into tbl1 values('goodbye', 20);\\nsqlite> select * from tbl1;\\nhello!|10\\ngoodbye|20\\nsqlite> CREATE TABLE tbl2 (\\n   ...>   f1 varchar(30) primary key,\\n   ...>   f2 text,\\n   ...>   f3 real\\n   ...> );\\nsqlite> .exit
\\n

To get to know sqlite commands, use the command: .help.

\\n

To exit sqlite, use the command: .exit.

\\n

Drivers

\\n

SQLite has drivers for all supported runtimes.

\\n

Following are the most commonly used drivers:

\\n

Node.JS apps

\\n

node-sqlite

\\n

Rails apps

\\n

In your Gemfile, include the line:

\\n
gem 'sqlite3'
\\n

and in configs/database.yml, make sure you use:

\\n
adapter: sqlite3\\ndatabase: db/development.db
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"common_errors\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Common errors\",\n \"contents\": \"\\n
\\n

Common errors

\\n

Sometimes you run into issues when you run your project. Here you will find the most common issues and how to solve them.

\\n

Address in use or similar

\\n

The most common reason for an error thrown by your app stating that a port or address is in use is the fact that some process is already running/listening on that port/address. You need to take a look for those and kill the processes conflicting with your app:

\\n
// Find the process\\nlsof -i tcp:$PORT
\\n

If any relevant process is running you will get a list looking like this:

\\n
COMMAND PID   USER   FD   TYPE   DEVICE SIZE/OFF NODE NAME\\napache2 699 ubuntu    4u  IPv6 83213152      0t0  TCP *:http-alt (LISTEN)
\\n

You now can kill that proccess. Make sure you replace PID with the ID of the process.

\\n
// Kill the process\\nkill -9 PID
\\n

For the console wizards:

\\n
kill -9 $(lsof -i:$PORT -t)
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"creating_coffeescript_app\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Create a CoffeeScript Project\",\n \"contents\": \"\\n

Create a CoffeeScript Project

\\n

For this tutorial, we'll show you how to create and run a CoffeeScript project, entirely within the Cloud9 IDE. To run any coffeescript project, you'll need to first make sure to install the coffeescript module via the Node Package Manager (npm). We're going to walk you through how to do that with a sample project.

\\n

First, create a new project. Then, in the console, enter the following command:

\\n
git clone git://github.com/fjakobs/cloud9-coffeescript-example.git
\\n

This is a sample CoffeeScript application written by one of our developers. After cloning the project, you'll find three different files in the project tree: server.js, app.coffee, and README.md.

\\n

The README.md file contains instructions to install coffee-script using npm. We've integrated Node Package Manager into Cloud9 IDE to enable users to install Node programs. Thus, from the Cloud9 IDE command line, type the following command to install the Coffeescript module:

\\n
npm install coffee-script
\\n

Next, let's have a look at the server.js file. The first line is the require() function, which is used to load the coffee-script module that you have just installed. On the second line, we declare the CoffeeScript file that contains your application. In the last line, we specify the port the server is listening to. When projects run within Cloud9 IDE, you must retrieve the port information using process.env.PORT.

\\n

Now, let's look at what the CoffeeScript file does. It creates an HTTP server with a function that is called for each request. In the callback function, you create a response with a status code of 200 (indicating that the request was fulfilled successfully) and the message "Hello World". You use module.exports to enable the server.js file to use the code in the CoffeeScript file:

\\n
http = require \\\"http\\\"\\n\\nmodule.exports = http.createServer((req, res) ->\\n    res.writeHead 200, 'Content-Type': 'text/plain'\\n    res.end 'Hello World\\\\n'
\\n

Next, run the server.js file and open the URL indicated in the console:

\\n

\\\"Messages

\\n

The result is:

\\n

\\\"The

\\n

To stop your application, go back to the editor and click on the \\\"Icon button in the Menu Bar.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"editing_wordpress_sites\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Editing Remote WordPress Websites via FTP\",\n \"contents\": \"\\n

Editing Remote WordPress Websites via FTP

\\n
\\n\\n
\\n\\n

Did you know that you can use Cloud9 IDE to work on your WordPress website? It's true, and incredibly easy. You can't edit your posts on WordPress using Cloud9, since they are stored in a database on your server. But you can edit pretty much every other aspect of your site.

\\n

To start, you'll need to create a new FTP project. After that, enter your wp-content folder, find the theme you're using on your website, and start editing its style.

\\n

Thanks to the preview button in the menu bar, you can also witness your changes as they happen, before committing them to your server.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"installing_npm_modules\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Installing NPM Modules\",\n \"contents\": \"\\n

Installing NPM Modules

\\n

Since Cloud9 IDE is built on top of Node.js, we also leverage the module system NPM. In Cloud9, you can install any npm package either locally or globally. Note that due to security restrictions, modules installed globally can only be used in the project they were installed from. In other words, while you have access to any command line tools installed by the module, they are bound to the project, not your username. We run version 1.1.24 of npm.

\\n

To demonstrate the power of NPM, we'll build and run a quick express server:

\\n
    \\n
  1. Launch the command line by hitting Shift-Escape. You can also go to View > Command Line if it's not visible.
    2. \\n
  2. Type npm install express, and wait for the npm install process to complete.
    3. \\n
  3. Create a new JavaScript file, and paste the following code:
    4. \\n
\\n
var express = require('express'),\\n    app = express();\\n\\napp.use(express.logger());\\n\\napp.get('/', function(req, res){\\n    res.send('Hello World');\\n});\\n\\napp.listen(process.env.PORT);\\nconsole.log('Express server started on port %s', process.env.PORT);
\\n

To launch your express server, click on the \\\"The button in the menu bar.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"installing_python_packages\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Installing Python Packages\",\n \"contents\": \"\\n

Installing Python Packages

\\n

Cloud9 supports the installation of Python packages for applications that need to go beyond the standard library set. Every workspace has version 0.6.10 of Python's easy_install package manager. For more information on this module, see the official easy_install documentation.

\\n

Let's try installing a package. First, type the following in the console:

\\n
easy_install markdown
\\n

This installs the markdown Python package to your workspace. You won't see the package installed in the directory tree, because it's kept deep within your project's the Python libs.

\\n

Next, create a new Python script, and add these lines of code:

\\n
import markdown\\n\\nhtml = markdown.markdown(\\\"# HELLO THERE!\\\")\\n\\nprint html
\\n

After clicking run, the console will correctly print out <h1>HELLO THERE!</h1>.

\\n

You have access to all of the functionality easy_install provides you. For example, you can open up the Python REPL and type the following to see a list of your installed packages:

\\n
>>> help('modules')
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"installing_ruby_gems\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Installing Ruby Gems\",\n \"contents\": \"\\n

Installing Ruby Gems

\\n

Cloud9 supports the installation of Ruby gems in your workspace using the RubyGems package manager. The current installed RubyGems version is 1.3.7. For more information on the gem command, see the official RubyGems documentation.

\\n

Let's try installing a gem. First, type the following in the console:

\\n
gem install progressbar
\\n

This installs the progressbar Ruby gem to your workspace. You won't see the gem installed in the directory tree, because it's kept deep within your project's the Ruby libs.

\\n

Next, create a new Ruby script, and add these lines of code:

\\n
require 'progressbar'\\n\\nbar = ProgressBar.new(\\\"Example progress\\\", 50)\\ntotal = 0\\nuntil total >= 100\\n  sleep(rand(2)/2.0)\\n  increment = (rand(6) + 3)\\n  bar.inc(increment)\\n  total += increment\\nend
\\n

After clicking run, the console will start printing out an ASCII progressbar.

\\n

You have access to all of the functionality gem provides you. For example, you can open up the console and type gem query to see a list of your installed gems.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"running_a_rails_app\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Running a Rails App\",\n \"contents\": \"\\n
\\n

Running a Rails App

\\n

Cloud9 IDE also supports the ability to run a Rails application. The rails command is only available on the terminal.

\\n

To run a rails application:

\\n
    \\n
  1. Open the terminal and type gem install rails
    2. \\n
  2. When done, type rails new example -d mysql
    3. \\n
  3. Edit your database configuration in configs/database.yml
    4. \\n
  4. Type rails s -b $IP -p $PORT
    5. \\n
\\n

That's it! Your rails app will now be running.

\\n

Note:

http://<workspacename>-c9-<username>.c9.io should be running your application.\\n\\n
\\n

Do not try to access the project through the IP address and port number rails returns to you--it won't work!

\\n

Use MySQL in your rails app

\\n
    \\n

  1. Setup MySQl - note your DB connect parameters

    \\n
    2. \\n

  2. edit configs/database.yml

    \\n
    3. \\n
\\n
development:\\n  adapter: mysql2\\n  encoding: utf8\\n  database: c9\\n  username: <%=ENV['C9_USER']%>\\n  host: <%=ENV['IP']%>
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"running_and_debugging_code\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Running and Debugging Your Code\",\n \"contents\": \"\\n
\\n

Running and Debugging Your Code

\\n

Cloud9 IDE provides several ways to run and debug your code. We'll explore each of them in this section of the documentation.

\\n

Note:

Currently, only Javascript/Node.js applications can make use of the debugger. You can also execute Javascript/Node.js, Python, Ruby, and Apache+PHP applications.\\n\\n
\\n

The following information applies to all of the above programming languages.

\\n

Running Code

\\n

Running your code in Cloud9 is really easy. First, open the file you want to run. Usually, this file is going to be the main entry point to your app; for example, if you're creating a server, you'd want to run the file that actually instantiates that server.

\\n

There are two ways to run your code: either through the Run Panel, or through the run button in the menu bar.

\\n

Using the Run Panel

\\n

Next, click on the Run button in the project bar. You'll notice immediately that your active file is already available to run. Just double-click on the file, and you'll launch your app.

\\n

When you're ready to stop your app, click on the \\\"Icon button in the menu bar at any time.

\\n

At the bottom of the run panel, you'll notice a few more options you can set. Filling these textboxes out creates a run scenario, which is like setting up some configurations for the way your code runs. These options are:

\\n
    \\n
  • Name the name of your run scenario
    • \\n
  • File Path: the location of your running file in your project
    • \\n
  • Runtime: defines how you want your code to be run. Typically, you'd set different runtime versions here.
    • \\n
  • Cmd Line Args: allows you to provide any additional command line arguments you want to pass to your app
    • \\n
\\n

Of course, you can also save your run scenarios; just click on the add button at the top of the panel. When you're ready to run a scenario, click on its name in the Run panel list. To remove a run scenario, click on its name in the run panel list, and then click on the remove button.

\\n

Using the Run Button

\\n

The run button in the menu bar acts as a sort of short cut to the Run panel. When clicked, the button automatically runs the currently active file. If you have a list of run scenarios already defined, the run button also presents a list of those:

\\n

\\\"Run

\\n

Run in debug mode indicates that you want to run the current code through the debugger. Auto show & hide debug tools will reveal (or collapse) the debugging tools panel described below. You can also work with this presentation by going to View > Panels, and configuring the debugger there.

\\n

Console Output

\\n

Every time you run a project, the console expands to reveal output from your program. If you're launching a server, Cloud9 provides you with a URL to access the project. Otherwise, any statements sent by your application's print statements (like console.log() for Javascript, print for Python, or puts for Ruby) are also shown here. For example:
\\\"Console

\\n

Debugging Your Code

\\n

Setting up a project to debug is done in very much the same way as running your code. The only difference is that you must click on the run settings icon in the Run panel \\\"Run and select Run in debug mode. Similarly, you can select Run in debug mode from the run button.

\\n

Initially, the only difference this will make is the expansion of the debugging toolbar to the right of the editor:
\\\"The

\\n

This toolbar, however, grants you the following capabilities:

\\n
\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
Toolbar IconDebugging FunctionDescription
\\\"DebuggingDebugging NavigationThis is a set of tools you can use to move around your code while debugging. You can step into, over, and out of your code, or simply press play to run the process until the next breakpoint.
\\\"IconCallstackThis is a structured list of information about the sequences of your code--basically, which functions are calling what, and where you are in the current process. It also stores local variables and function arguments, if present. You can use this feature to check how your code is running:
\\\"Callstack
\\\"IconInteractive ModeLets you evaluate a piece of code, such as expressions or the values and properties of variables. The text field allows you to type any code you want, in case you discover a way to fix you problem:\\n\\\"Interactive
\\\"IconVariable InspectionThis shows all the related variables (including functions) that are present in the current context:\\n\\\"Variable
\\\"IconBreakpoint ListAt any point during your coding or debugging session, you can click on the gutter to apply a breakpoint: \\\"Breakpoint. When debugging your code, the process pauses at your established breakpoints, so that you can inspect closely what's going on in a certain part of the code. You can click on the breakpoint list to view all the breakpoints in your workspace. If you click on the checkbox, you can enable or disable a breakpoint as well. You can also click on a breakpoint in the gutter to disable or enable it.
\\n

While debugging, you also have the power of the live inspector. While hovering over a piece of code in the editor, you'll instantly get some floating text that describes the values of that variable, similar to Variable Inspection.
\\\"Live

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"running_wordpress_on_cloud9\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Running WordPress on Cloud9\",\n \"contents\": \"\\n
\\n

Running WordPress on Cloud9

\\n

WordPress is web software you can use to create websites or blogs.\\nYou can develop and host WordPress websites entirely on Cloud9 IDE

\\n

Creating a wordpress workspace

\\n

Create a WordPress workspace from the WordPress template on your Cloud9 dashboard

\\n

Note:

We will download, extract and configure WordPress for you.\\n\\n
\\n

In order to run WordPress, you need a database to host your posts, articles, etc.

\\n

You can use MySQL with our utility script mysql-ctl as explained in MySQL Setup

\\n

Running the website

\\n

To start MySQL server and create the required database, type in the terminal:

\\n
mysql-ctl start
\\n

Open index.php in your workspace root and click the Run button

\\n

You can check the generated config for you In wp-config.php (you don't need to change anything there)

\\n
define('DB_NAME', 'c9');\\ndefine('DB_USER', getenv('C9_USER'));\\ndefine('DB_PASSWORD', '');\\ndefine('DB_HOST', getenv('IP'));\\ndefine('WP_SITEURL', 'http://' . getenv('C9_PROJECT') . '.' . getenv('C9_USER') . '.c9.io');
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"terminal_monitor\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"The Terminal Monitor\",\n \"contents\": \"\\n

The Terminal Monitor

\\n

Many times your app returns errors which are hard to understand and even harder to resolve. This is where the Terminal Monitor comes in.\\nThe following video gives a quick overview of the features and how the Terminal Monitor helps you write better apps.

\\n\\n\\n

If you would like to propose additions or help which Terminal Monitor should provide, please send a message to support@c9.io

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"writing_a_go_app\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Writing a Go App\",\n \"contents\": \"\\n
\\n

Writing a Go App

\\n

Cloud9 IDE doesn't provide out-of-the-box support for the Go language, but with \\na few quick steps you can set up Cloud9 to build and run apps in Go!

\\n

Create a new workspace

\\n

First, create a new Custom workspace and call it whatever you want:

\\n

\\\"Create

\\n

After your new workspace is created, click the "start editing" button. At the \\nbottom of your workspace you will see the Terminal. If you prefer to have it\\nfullscreen, you can launch a terminal tab by pressing Alt-T, or from the menu: \\nView > Terminals > New Terminal.

\\n

From the terminal you can install & setup everything on the underlying virtual \\nenvironment that every workspace is provided with.

\\n

Download Go

\\n

When you first enter your Terminal, you will be in your workspace root folder, \\nwhich is a number such as ~/562166. Make a note of this directory name, as \\nyou'll need it later.

\\n

Let's use your home directory to download the Go distribution; to get there, \\nsimply enter the following in the Terminal:

\\n
cd ..
\\n

To download the Go distribution enter the following:

\\n
wget https://go.googlecode.com/files/go1.1.1.linux-amd64.tar.gz
\\n

Note:

at the time of writing the latest version was 1.1.1, but you might want to \\nuse a new version if it has become available. \\n\\n
\\n

After the download is complete, extract the archive:

\\n
tar -xzf go1.1.1.linux-amd64.tar.gz
\\n

Once the extraction is done, you will notice a new go directory in your home \\ndirectory. Feel free to delete the archive file you downloaded.

\\n

Set up your environment

\\n

The last step is to configure the environment so it can see the Go distribution \\nas well as our workspace Go files. To do this, edit your bash configuration \\nin the Terminal using vim (or emacs, nano, any simple editor will do):

\\n
vim ~/.bashrc
\\n

Add the following lines to your .bashrc file:

\\n
# setup go configuration \\nexport GOROOT=$HOME/go \\nexport PATH=$PATH:$GOROOT/bin \\n\\n# setup workspace t\\nexport GOPATH=$HOME/562166 \\nexport PATH=$PATH:$GOPATH/bin
\\n

Update the GOPATH line above to use the workspace directory you noted earlier \\n(so don't use $HOME/562166).

\\n

After you save your .bashrc file, load the new settings:

\\n
source ~/.bashrc
\\n

That's it! You should be good to Go (pun intended).

\\n

Note:

Thanks to Scotty Moon for writing an article about Go on Cloud9 IDE\\nand letting us use it for documentation!
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"writing_a_php_app\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Writing a PHP App\",\n \"contents\": \"\\n
\\n

Writing a PHP App

\\n

With Cloud9 IDE, you can run your PHP pages, without relying on a third-party system like Apache hosting. We run PHP version 5.3.3.

\\n

You can choose to run PHP scripts via the command line, by typing php, followed by the name of your PHP file. However, this is not a very common use case. Most likely, you'll be running your own server and hosting PHP files.

\\n

Here's a simple demonstration. First, create a PHP file called hello_world.php, and paste this code into it:

\\n
<html>\\n  <head>\\n   <title>PHP Test</title>\\n  </head>\\n  <body>\\n   <?php echo '<p>Hello World</p>'; ?> \\n  </body>\\n</html>
\\n

Next, open the Run & Debug panel, at the left of the IDE. From the Runtime dropdown, select Apache+PHP. Then, click on the \\\"The button in the top menu bar.

\\n

The console should now spit out a message about how your Apache server is running, something similar to this:

\\n
Running Apache Process\\nTip: you can access long running processes, like a server, at 'http://php_hello.gjtorikian.c9.io'.
\\n

Clicking on that link gets you to your PHP page. For a more in-depth workflow, see the article on running WordPress entirely on Cloud9.

\\n

Modifying php.ini

\\n

You can configure your PHP installation by editing the php.ini located in the /home/ubuntu/workspace directory. Please note: in some cases php.ini is located somewhere else. Just create a simple PHP file running phpinfo() to find out where to look for php.ini.

\\n

Make sure to restart Apache after you have applied your changes

\\n
apachectl restart
\\n

Note:

Currently, you can't debug PHP applications yet, but we are working on adding this feature.\\n
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"writing_a_python_app\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Writing a Python App\",\n \"contents\": \"\\n

Writing a Python App

\\n

While using Cloud9 IDE, you have access to the Python runtime. Accessing the command is no different than the way you'd use Python on your computer; just open the command line and type python. Currently, we run version 2.6.6.

\\n

To run a Python program that you've created, you can either:

\\n
    \\n
  • Open the command line and type python, followed by the name of your program; for example python hello_world.py
    • \\n
  • Create a new run scenario, so that you can do things like pass in command line arguments
    • \\n
\\n

As a quick demonstration, open a new file, and paste this Python code into it:

\\n
#!/usr/bin/python\\n\\nprint \\\"Hello World!\\\";
\\n

When you hit the \\\"The button in the menu bar, the console will print out Hello World!.

\\n

Note:

Currently, you can't debug Python applications, but we are working on adding this feature.
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"writing_a_ruby_app\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Writing a Ruby App\",\n \"contents\": \"\\n
\\n

Writing a Ruby App

\\n

While using Cloud9 IDE, you have access to the Ruby runtime. Accessing the command is no different than the way you'd use Ruby on your computer; just open the command line and type ruby. Currently, the default version is 1.9.3.

\\n

To run a Ruby program that you've created, you can either:

\\n
    \\n
  • Open the command line and type ruby, followed by the name of your program; for example ruby hello_world.rb
    • \\n
  • Create a new run scenario, so that you can do things like pass in command line arguments
    • \\n
\\n

As a quick demonstration, open a new file, and paste this Ruby code into it:

\\n
#!/usr/bin/ruby\\n\\nputs 'Hello world'
\\n

When you hit the \\\"The button in the menu bar, the console will print out Hello world.

\\n

Note:

Currently, you can't debug Ruby applications, but we are working on adding this feature.\\n\\n
\\n

RVM Support

\\n

We have rudimentary support for rvm, that allows you only to switch between versions 1.8.7 and 1.9.3. We don't support rvm per-project or global gemsets.

\\n

To use rvm, open the terminal and type:

\\n
# to switch to version 1.8.7\\nrvm use 1.8\\nrvm use 1.8.7 \\n\\n# to switch to version 1.9.3\\nrvm use 1.9\\nrvm use 1.9.3
\\n

However, if you like, you can install the "real" rvm by executing the following command in the terminal:

\\n
curl -L https://get.rvm.io | bash -s stable
\\n

To grab the latest rvm AND the latest Ruby version, type:

\\n
curl -L https://get.rvm.io | bash -s stable --ruby
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"creating_new_workspace\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Creating a New Workspace\",\n \"contents\": \"\\n
\\n

Creating a New Workspace

\\n

Cloud9 supports three types of workspaces:

\\n
    \\n
  1. Hosted
    2. \\n
  2. FTP
    3. \\n
  3. SSH
    4. \\n
\\n

In this article, we'll walk you through the creation of a new workspace and describe the choices you encounter.

\\n

The first step for creating a new workspace is click the "CREATE NEW WORKSPACE" button in your Dashboard:

\\n

\\\"New

\\n

At this point, you'll encounter two choices: Create a new workspace and Clone from URL. Here's what they mean:

\\n
    \\n
  • Create a New Workspace allows you to create any of the previously mentioned types of workspaces (hosted, FTP, or SSH).
    • \\n
  • Clone from URL allows you to instantly create a workspace from a repository, like GitHub or Bitbucket, using its URL. We'll explain more about this in the section below.
    • \\n
\\n

Create a New Workspace

\\n

After clicking on Create a new workspace, you're taken to the screen below:

\\n

\\\"Options

\\n

First, let's enter a workspace name.\\nDepending on whether you have a Free of Premium account, you can choose to make it either Public (open to anyone with the URL), or Private (only accessible to you and people you share it with).

\\n

After this, choose the type of workspace you want to create:

\\n
    \\n
  • Hosted: This is a regular Cloud9 workspace, powered by a full Ubuntu environment. You even have sudo powers! This is the best choice for most people, and we've included some more info about it below.
    • \\n
  • FTP allows you to upload your files directly to an FTP server that you have access to
    • \\n
  • SSH, also called the "bring your own server" feature, lets you log into a server you own and run Cloud9 from there
    • \\n
\\n

Make a choice for the type of workspace and press Create. That's it! You can now see your new workspace in the dashboard:

\\n

\\\"New

\\n

Now, just click Start Editing to get started!

\\n

Hosted workspaces

\\n

Choose this workspace type to start from scratch with a 'Custom' workspace, or simply pick a pre-configured environment like Node.js, WordPress, or Python/Django, and immediately start developing your app.\\nThis way you don't need to spend valuable development time on system setup and maintenance, as we maintain it, and you control it.

\\n

\\\"Options

\\n

As it's powered by a full Linux Ubuntu environment, hosted workspaces allow you to install any package (sudo apt-get install package), run git commands from the console to push your changes to a GitHub repo or a Bitbucket git repo, etcetera.

\\n

Cloning from a URL

\\n

The second option for creating a new workspace is to clone one from URL. The URL would be, for example, the URL of a GitHub workspace.

\\n

In fact, let's clone a workspace. When you click on Clone from URL, you're taken to this screen:

\\n

\\\"Options

\\n

Paste the following GitHub URL in the textbox labeled Source URL: https://github.com/mattpardee/geekdots

\\n

If you have a premium account, you can choose who has access to your workspace. For regular users, the new workspace will be public.

\\n

Now, check out the workspace. It will be created under My Workspaces. You can now start editing it!

\\n

Deleting a Workspace

\\n

Now that you know how to create a workspace, you should also learn how to delete one. Look at the far right side of your dashboard:

\\n

\\\"Delete

\\n

Clicking on the Delete button prompts the IDE to ask for confirmation:
\\\"Confirmation

\\n

This is your last chance to change your mind. Once you have typed delete in the textbox and pressed the red button, your workspace will be gone forever from Cloud9. If you are sure you want to delete your workspace, go ahead and press the red button. Of course, if your workspace is hosted elsewhere, like on another git or FTP server, it still exists in those repositories.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"writing_nodejs_hello_world\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Writing and Running a Node.js Program\",\n \"contents\": \"\\n
\\n

Writing and Running a Node.js Program

\\n

Cloud9 IDE was built on top of the Node.js platform, and as such, you have full access to the node runtime. Currently, we support running both version v0.6.x and v0.8.x.

\\n

In this section, we'll walk you through the creation of a simple Hello World program. To get started, you'll first need to create a (GitHub or Mercurial) project. If you need a refresher on how to do this, please refer to Creating a New Workspace.

\\n

A Simple Node.js HTTP Server

\\n

Once you're in Cloud9, create a new file called server.js. Type the following code in the file:

\\n
var http = require('http');\\nhttp.createServer(function (req, res) {\\n    res.writeHead(200, {'Content-Type': 'text/plain'});\\n    res.end('Hello World\\\\n');\\n}).listen(process.env.PORT, process.env.IP);
\\n

This is a Node.js HTTP server. It returns a simple "Hello World" page every time you access the page. In short, you are creating an HTTP server with a callback function that is called for each request.

\\n

In the callback function, you create a response with a status code of 200 (indicating that the request was fulfilled successfully) and the message "Hello World". Finally, you specify which port and IP address the server runs on. When Cloud9 IDE runs servers, you set and retrieve the IP address and port number with the process.env.IP and process.env.PORT variables.

\\n

When you hit the \\\"The button in the menu bar, the console will print out the following message:
\\\"Console

\\n

To see your application in action, click on the link created for your project. You should see your "Hello World" application open up in a new browser tab:
\\\"Node.js.

\\n

NVM Support

\\n

We have rudimentary support for nvm, that allows you only to switch between Node.js versions 0.6.21 and 0.8.x.

\\n

To use nvm, open the terminal and type:

\\n
# to switch to version 0.6.21\\nnvm use v0.67 \\n\\n# to switch to the latest 0.8.x\\nnvm use v0.8
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"ftp_workspaces\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Setting up an FTP project\",\n \"contents\": \"\\n

Setting up an FTP project

\\n
\\n\\n
\\n\\n

In this article, we'll show you how to set up an FTP project.

\\n

Note:

Currently, Cloud9 IDE only supports passive FTP. Active FTP, SFTP and FTPS are not yet supported. For SSH connections, consider creating an SSH workspace.\\n\\n
\\n

To create an FTP project, go to the Dashboard and click on the \\\"Project next to MY PROJECTS. Choose the option to Create a new project (see "Creating a New Project" if you need to review the steps to create a new project):
\\\"New

\\n

In the pop-up window that appears, select FTP for the project type:

\\n

\\\"FTP

\\n

Let's review the options available for your FTP project:

\\n
    \\n
  • Hostname: the domain name or IP address of the machine running your FTP server.
    • \\n
  • Username: your username for the FTP server.
    • \\n
  • Password: your password for the FTP server.
    • \\n
  • Initial path: this is an optional parameter. You can set it as an absolute (starts with /) path. Otherwise, it'll be set to a relative path, and Cloud9 assumes that you want to start from the folder your FTP server leaves you after login (home or default folder).
    • \\n
\\n

Warning:

Be careful not to put an initial path that leaves you in a location where you don't have write privileges as that could cause problems.\\n\\n
\\n

Fill in your FTP details and click the Login Test to verify that the settings are correct. If the test succeeds, go ahead and click Create to create your FTP project. You'll then see your project in the Dashboard under My Projects:

\\n

\\\"New

\\n

When your new FTP project is selected, you will see three buttons: Start Editing, FTP settings, and Delete (on the far right). FTP settings gives you access to the settings you just filled in, as well as the login test. This is useful to use in case your login credentials have changed.

\\n

To get started with your FTP project, click on the Start Editing button. You'll be taken to the editor. Under Project Files, you should see the files from the FTP server in the directory you selected (either your home/default folder or the location indicated by the Initial Path, if you set it). The editor for FTP projects works the same as in other projects: you can create and edit your files in the usual way. The main difference is the FTP log at the bottom of the page (where the console is usually located for other non-FTP projects).

\\n

The FTP log displays output related to the interaction with the FTP server. The screenshot below, for example, shows what happens when we create a new file called TestFile.txt. The file is created in the FTP server and when I write to it, the contents are transferred.

\\n

\\\"Demonstrating

\\n

Note:

In an FTP project, all files are stored on your FTP server; Cloud9 only stores the FTP settings. Please keep this in mind. Cloud9 IDE does not keep any copies of your files, so make sure you back them up properly. Any changes you make to these files in Cloud9 are automatically reflected on the live web server.
\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"run_your_own_workspace\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Running Your Own SSH Workspace\",\n \"contents\": \"\\n
\\n

Running Your Own SSH Workspace

\\n

You have access to an incredibly powerful feature of Cloud9 that we like to call "running your own workspace."

\\n

If you own a server that you can SSH into, you can log into that machine with Cloud9 and work on your projects remotely. To put this into perspective, you could have an entire toolchain set up on this machine--say, make with gcc, or ant with Java--edit the files with Cloud9 IDE, and build your toolchain via the IDE's terminal. Here's a video demonstrating how you could instantly compile a C program using an SSH workspace and Cloud9:

\\n
\\n\\n
\\n\\n

Connection Prerequisites

\\n

In order to connect Cloud9 with a server you own, you'll need two things:

\\n
    \\n
  1. Node.js installed on the server. This version must be between Node.js version 0.6.16 and the latest 0.8.x.
    2. \\n
  2. Your public SSH key must be saved on the server at ~/.ssh/authorized_keys. This is to ensure the utmost security between your client computer and the machine you're attempting to access. Cloud9 provides you with your SSH key in the workspace dialog; it is up to you to save it to the appropriate path. For more information on SSH keys, see this article.
    3. \\n
\\n

Tip:

If you're behind a firewall, you can identify which IP address and port Cloud9 is running on by typing echo $OPENSHIFT_INTERNAL_IP and echo $OPENSHIFT_INTERNAL_PORT into the console. You can use this information to open any blocked connections.\\n\\n
\\n

Creating an SSH Workspace

\\n

Once you've got those requirements set up, here's how you can create an SSH workspace of your own:

\\n

In the Projects tab on the Dashboard, click on the \\\"Project next to MY PROJECTS and choose the option to Create a new project (see "Creating a New Project" if you need to review the steps to create a new project):
\\\"New

\\n

In the pop-up window that appears, select SSH for the project type:
\\\"SSH

\\n

You don't need to fill out every option provided by the dialog. Let's review what they are:

\\n
    \\n
  • Hostname: the domain name or IP address of the machine running your SSH server.
    • \\n
  • Username: your username for the SSH server.
    • \\n
  • Node.js Binary Path: the locaton of your Node.js binary. If you're not sure where it is, you can always let Cloud9 guess it for you. Otherwise, on your server, type which node, to see the full path
    • \\n
  • Initial path: this is an optional parameter. You can set it as an absolute (starts with /) path. Otherwise, it'll be set to a relative path, and Cloud9 assumes that you want to start from the folder your SSH server leaves you after login (usually the home or default folder).
    • \\n
  • Port: this is an optional parameter. Cloud9 will automatically try to connect on port 22
    • \\n
\\n

Warning:

Be careful not to put an initial path that leaves you in a location where you don't have write privileges, as that could cause problems!\\n\\n
\\n

Fill in your SSH details and click the Login Test to verify that the settings are correct. If the test succeeds, go ahead and click Create to create your SSH connection. You'll then see your project in the Dashboard under My Projects:\\n\\\"New

\\n

When your new SSH is selected, you will see three buttons: Start Editing, SSH settings, and Delete (on the far right). SSH settings gives you access to the settings you just filled in, as well as the login test. This is useful to use in case your login credentials have changed.

\\n

Warning:

Make sure that you copied your SSH key correctly! Trailing spaces are significant, so make sure your text editor on your server is not modifying the key that Cloud9 is providing you with.\\n\\n
\\n

To get started with your SSH project, click on the Start Editing button. You'll instantly be taken to the editor, and have full access to your server's resources. As you can see in the video above, this means you can do exciting things like compiling C programs.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_bitbucket_workspace\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Setting Up a Bitbucket Workspace\",\n \"contents\": \"\\n
\\n

Setting Up a Bitbucket Workspace

\\n

Bitbucket is a code-hosting services that offers both git and mercurial support. Projects can be listed as private or public, absolutely free. For more information on Bitbucket, visit https://bitbucket.org.

\\n

We have integrated Bitbucket into the IDE to enable you to easily work on your public and private repositories. The following article explains how you can activate your Bitbucket account in Cloud9 IDE.

\\n

Bitbucket Activation

\\n

You can manage your add-on services from your user profile that you can find in the dashboard. When you have just signed in, click Your Account on the top of the left-side panel. Here, you can change the settings of your account. At the bottom, you'll see a list of add-on services that are integrated into Cloud9 IDE. Click activate on the Bitbucket button:

\\n

\\\"Add-on

\\n

A new window will pop-up on your screen. This window asks you to give authorization permission for the Cloud9 IDE application to interact in various ways with Bitbucket:

\\n

\\\"Bitbucket

\\n

To finalize the activation, click on Allow. Next, you're redirected to your account page, where you'll notice that your Bitbucket account is activated. You can deactivate Bitbucket by simply clicking deactivate, which may be useful when you want to link your Bitbucket account to another Cloud9 account.

\\n

Now that you have activated Bitbucket, you can start to create and manage your projects!

\\n

Managing Projects

\\n

There are several ways to manage Bitbucket projects in Cloud9 IDE:

\\n
    \\n
  • By creating a new git or mercurial project and pushing it to Bitbucket
    • \\n
  • By cloning a Bitbucket project from a URL
    • \\n
  • By bringing in a Bitbucket project manually
    • \\n
\\n

Creating a New Git Project

\\n

New projects are created from the dashboard. In the left-side panel, click on the \\\"Project to add a new project:

\\n

\\\"New

\\n

A new window will pop-up in which you can change your settings to your preferences:

\\n
    \\n
  • Fill in your preferred project name in the text field
    • \\n
  • Choose who will have access to the project (a feature for Premium customers)
    • \\n
  • Select your project type (git, mercurial, or FTP)
    • \\n
  • Choose a development server (a feature for Premium customers)
    • \\n
\\n

\\\"New

\\n

After you click CREATE, the project is listed in your dashboard. Select the project to see its Project Profile, where you can start editing: \\\"Start

\\n

There are a couple of things you should do first, before you can use all of git's power. First, you'll want to add a remote to the project. From the Cloud9 IDE command line, you can execute the following commands:

\\n
git remote add [remote name] [remote url]
\\n

remote url is the location of the project on Bitbucket; for example 'origin git@bitbucket.org:username/repository_name.git'. You'll have to create a Bitbucket project first in order to generate this URL. Adding a remote URL lets you freely push and pull your project.

\\n

Next, create a few new files inside your project. By default, you should already have a README.md. You can add these files to git with the following command:

\\n
git add [file1, file2, file3, ...]
\\n

Finally, create a commit that you can push to your remote:

\\n
git commit -m 'added new files'
\\n

Don't forget to push this commit out to Bitbucket:

\\n
git push [remote name] master
\\n

Ta-da! Your project is developed on Cloud9, and stored in Bitbucket.

\\n

Cloning Projects from a URL

\\n

You can also create a project in Cloud9 IDE by cloning it from a URL. Once again, click on the \\\"Project, and select Clone from URL. A new window pops up, asking you:

\\n
    \\n
  • to enter a Source URL
    • \\n
  • to choose who will have access to the project (Premium feature)
    • \\n
  • to choose a development server (Premium feature)
    • \\n
\\n

\\\"Clone

\\n

You can find an examples of a Bitbucket URL on any of their repo description pages:

\\n

\\\"Bitbucket

\\n

Paste the URL in the source field and click CHECKOUT. In the left-side panel, you'll see the project and its status turn into "Cloning in Progress". When this process is completed you can open the project and start editing it, just like any other project.

\\n

Clone Projects Already On Bitbucket

\\n

When you provide Cloud9 IDE with your Bitbucket credentials, it provides a list of projects you haven't yet imported into the editor:

\\n

\\\"Bitbucket

\\n

From this list, clicking on a project and selecting CLONE TO EDIT brings the repo into the IDE, just as if you cloned it from a URL.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_github_workspace\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Setting Up a GitHub Workspace\",\n \"contents\": \"\\n
\\n

Setting Up a GitHub Workspace

\\n

GitHub is a code hosting service which offers you a lot of features to manage your public and private git repositories. For more information about GitHub and how to use it, visit https://github.com.

\\n

We have integrated GitHub into the IDE to enable you to easily work on your public and private Git repositories. The following article explains how you can activate your GitHub account in Cloud9 IDE.

\\n

GitHub Activation

\\n

You can manage your add-on services from your user profile that you can find in the dashboard. When you have just signed in, click Your Account on the top of the left-side panel. Here, you can change the settings of your account. At the bottom, you'll see a list of add-on services that are integrated into Cloud9 IDE. Click activate on the GitHub button:

\\n

\\\"Add-on

\\n

A new window will pop-up on your screen. This window asks you to give authorization permission for the Cloud9 IDE application to interact in various ways with GitHub:

\\n

\\\"GitHub

\\n

To finalize the activation, click on Allow. Next, you're redirected to your account page, where you'll notice that your GitHub account is activated. You can deactivate GitHub by simply clicking deactivate, which may be useful when you want to link your GitHub account to another Cloud9 account.

\\n

Now that you have activated GitHub, you can start to create and manage git projects!

\\n

Managing Git Projects

\\n

There are several ways to manage GitHub projects in Cloud9 IDE:

\\n
    \\n
  • By creating a new git project and pushing it to GitHub
    • \\n
  • By cloning a GitHub project from a URL
    • \\n
  • By bringing in a GitHub project manually
    • \\n
\\n

Creating a New Git Project

\\n

New projects are created from the dashboard. In the left-side panel, click on the \\\"Project to add a new project:

\\n

\\\"New

\\n

A new window will pop-up in which you can change your settings to your preferences:

\\n
    \\n
  • Fill in your preferred project name in the text field
    • \\n
  • Choose who will have access to the project (a feature for Premium customers)
    • \\n
  • Select your project type (git, mercurial, or FTP)
    • \\n
  • Choose a development server (a feature for Premium customers)\\n{: #setupOptions}
    • \\n
\\n

\\\"New

\\n

Select git as your project type. After you click CREATE, the project is listed in your dashboard. Select the project to see its Project Profile, where you can start editing: \\\"Start

\\n

There are a couple of things you should do first, before you can use all of git's power. First, you'll want to add a remote to the project. From the Cloud9 IDE command line, you can execute the following commands:

\\n
git remote add [remote name] [remote url]
\\n

remote url is the location of the project on GitHub; for example 'git@github.com:/ajaxorg/node_chat'. You'll have to create a GitHub project first in order to generate this URL. Adding a remote URL lets you freely push and pull your project.

\\n

Next, create a few new files inside your project. By default, you should already have a README.md. You can add these files to git with the following command:

\\n
git add [file1, file2, file3, ...]
\\n

Finally, create a commit that you can push to your remote:

\\n
git commit -m 'added new files'
\\n

Don't forget to push this commit out to GitHub:

\\n
git push [remote name] master
\\n

Ta-da! Your project is developed on Cloud9, and stored in GitHub.

\\n

Cloning Projects from a URL

\\n

You can also create a project in Cloud9 IDE by cloning it from a URL. Once again, click on the \\\"Project, and select Clone from URL. A new window pops up, asking you:

\\n
    \\n
  • to enter a Source URL
    • \\n
  • to choose who will have access to the project (Premium feature)
    • \\n
  • to choose a development server (Premium feature)
    {: #cloningOptions}
    • \\n
\\n

\\\"Clone

\\n

You can find an examples of a GitHub URL on any of their repo description pages:

\\n

\\\"GitHub

\\n

Paste the URL in the source field and click CHECKOUT. In the left-side panel, you'll see the project and its status turn into "Cloning in Progress". When this process is completed you can open the project and start editing it, just like any other project.

\\n

Clone Projects Already On GitHub

\\n

When you provide Cloud9 IDE with your GitHub credentials, it provides a list of projects you haven't yet imported into the editor:

\\n

\\\"GitHub

\\n

From this list, clicking on a project and selecting CLONE TO EDIT brings the repo into the IDE, just as if you cloned it from a URL.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"ssh_workspaces\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"SSH Workspaces\",\n \"contents\": \"\\n
\\n

SSH Workspaces

\\n

To connect Cloud9 to a server via SSH, we first need to install a few dependencies on your system. \\nThis is done by an open-source installer which you can find here.

\\n

Usually the installation should succeed without any issues, but on some systems you will need to install a few dependencies manually. See below for common dependency issues you might run into.

\\n

Installing Python 2.7 on CentOS

\\n
curl -O https://www.python.org/ftp/python/2.7.6/Python-2.7.6.tar.xz\\ntar xf Python-2.7.6.tar.xz\\ncd Python-2.7.6\\n./configure --prefix=/usr/local\\nmake && make altinstall
\\n

Common errors

\\n

no configure: error: "curses not found"

\\n

To get around this issue make sure glibc-static is installed on the machine.

\\n\\n
\\n
\\n \"\n },\n {\n \"filename\": \"setting_up_gitlab_workspace\",\n \"mtime\": 1416491265000,\n \"pageTitle\": \"Setting Up a GitLab workspace\",\n \"contents\": \"\\n

Setting Up a GitLab workspace

\\n

GitLab is open source Git management software used by more than 25.000 \\norganizations, see http://gitlab.org/.

\\n

GitLab.com offers services for on-premise GitLab installations \\nand free private git repositoring on GitLab Cloud \\nwith unlimited repo's and collaborators.

\\n

To use your on-premise GitLab installation or GitLab Cloud please see \\nthe instructions for cloning from a url.

\\n\\n
\\n
\\n \"\n }\n ],\n \"toc\": \"\\n \\n \",\n \"baseUrl\": \"https://docs.c9.io\",\n \"title\": \"Cloud9 User Documentation\"\n}" }, { "filename": "setting_up_hosted_mysql", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "MySQL", "contents": "

MySQL

\n

MySQL is the world's most widely used open source relational database management system (RDBMS) that runs as a server providing multi-user access to a number of databases.

\n

MySQL's most common features

\n
    \n
  • A broad subset of ANSI SQL 99, as well as extensions
    • \n
  • Cross-platform support
    • \n
  • Stored procedures
    • \n
  • Triggers
    • \n
  • Cursors
    • \n
  • Updatable Views
    • \n
  • Information schema
    • \n
  • Many more
    • \n
\n

Using MySQL with Cloud9

\n

Cloud9 IDE does not support installing a MySQL database (yet). As a workaround you can choose to connect your project to a MySQL database hosted elsewhere. Xeround\noffers hosted MySQL instances and have a free tier available for getting started.

\n

Xeround

\n
    \n
  1. Register with Xeround
    2. \n
  2. Log in to your controlpanel
    3. \n
  3. Choose 'create new'
    4. \n
  4. Choose a datacenter
    5. \n
  5. Enter your Database name, Username and Password and create
    6. \n
  6. Select your newly created instance and click the 'External DNS Hostname' link provided to log into PHPMyAdmin
    7. \n
  7. Create and import/setup your database
    8. \n
\n

Cloud9

\n
    \n
  1. Log into your account
    2. \n
  2. Create a new project (or use an existing one)
    3. \n

  3. Test the connection using the following script:

    \n
             <?php\n\n         $database = new mysqli('instanceNo.db.xeround.com', 'username', 'password', 'databasename', 'port');\n\n         if($database->connect_errno > 0){\n             die ('Database Error' . $database->connect_error); \n         }else{\n             die ('Connected!');\n         }\n         ?>
    \n
    4. \n
  4. Save the file
    5. \n
  5. Run the file
    6. \n
\n

Source

\n

Courtesy of Roger Qui of Polycadamy. This guide is elaborately explained in a video tutorial

\n\n
" }, { - "filename": "project_bar", - "mtime": 1412172002000, - "pageTitle": "The Project Bar", - "contents": "\n

The Project Bar

\n

Note:

this article is outdated, a new version will follow soon\n\n
\n

The project bar is located towards the left of the Cloud9 IDE: \"The

\n

The buttons in the project bar allow you to reveal and hide panels for the IDE. In more detail:

\n
    \n
  • Pressing on the Cloud9 icon collapses the panel area
    • \n
  • Project Files shows your workspace's directory structure. You can view all your files here. Right-clicking within this panel reveals a drop-down menu with additional options, such as the ability to rename files or create new directories.
    • \n
  • Active Files lists your files that are currently open.
    • \n
  • Run & Debug lets you run and debug your code live, in the browser. For more information, see the section on "Running and Debugging Your Code".
    • \n
  • Deploy allows you to deploy to a variety of services. For more information, see the section on "Deploying Your Code".
    • \n
  • Preferences lets you change the behavior of the editor. The Preferences documentation is provided on its own page.
    • \n
\n

Clicking on any button expands its menu. Clicking on an expanded menu causes it to collapse, which gives you more room in the IDE to work with.

\n\n
" + "filename": "setting_up_mongodb", + "mtime": 1416491265000, + "pageTitle": "MongoDB", + "contents": "

MongoDB

\n

MongoDB is a scalable, high-performance, open source NoSQL database.

\n

MongoDB's most common features

\n
    \n

  • Document-Oriented Storage
    \nJSON-style documents with dynamic schemas offer simplicity and power.

    \n
    • \n

  • Full Index Support
    \nIndex on any attribute, just like you're used to.

    \n
    • \n

  • Querying
    \nRich, document-based queries.

    \n
    • \n
\n

In addition, MongoDB has many scalability features such as:

\n

Replication, Auto-sharding, Map/Reduce and GridFS

\n

Running MongoDB on a Cloud9 workspace

\n

MongoDB is preinstalled in your workspace. To run MongoDB, run the following below (passing the correct parameters to it). Mongodb data will be stored in the folder data.

\n
$ mkdir data\n$ echo 'mongod --bind_ip=$IP --dbpath=data --nojournal --rest \"$@\"' > mongod\n$ chmod a+x mongod
\n

You can start mongodb by running the mongod script on your project root:
\n$ ./mongod

\n

MongoDB parameters used:

\n

| Parameter | Description |\n| ------------------------------ | ----------------------------------------------------------------------------------------------- |\n| --dbpath=data | Because it defaults to /var/db which isn't accessible) |\n| --nojournal | Because mongodb usually pre-allocates 2 GB journal file (which exceeds Cloud9 disk space quota) |\n| --bind_ip=$IP | Because you can't bind to 0.0.0.0) |\n| --rest | Runs on default port 28017 |

\n

Drivers

\n

You should use the host $IP instead of localhost as your driver connection url.
\ne.g. in Node, it is: process.env.IP

\n

MongoDB has drivers for all supported runtimes. Following are the most commonly used drivers:

\n

Node.JS apps

\n

Mongoose
\nNode-Mongodb-Native

\n

Shell Access

\n

To access a shell prompt for the above MongoDB run the following.

\n
$ mongo
\n

Check out docs.mongodb.org for details on how to use the shell

\n\n
" }, { - "filename": "tab_functions", - "mtime": 1412172002000, - "pageTitle": "Tab Functions", - "contents": "

Tab Functions

\n

Note:

this article is outdated, a new version will follow soon\n\n
\n

Cloud9 IDE offers advanced tab features to make working with multiple files easy. By right-clicking on any tab, you'll open up the tab context menu:

\n

\"The

\n

These feature include:

\n
    \n
  • Reveal in File Tree: opens the current file in the Project Files tree
    • \n
  • Close Tab: closes the current tab
    • \n
  • Close All Tabs: closes all the opened files
    • \n
  • Close All But Current Tab: closes all the opened files, except the current one
    • \n
  • Close Tabs to the Right/Left: closes all opened tabs to the right (or left) of the current one
    • \n
  • File Revision History...: launches the revisions panel
    • \n
\n

To the left of the tab menu is another button that offers additional functions for tab navigation:
\"The

\n

Tab Sessions

\n
\n\n
\n\n

Tab sessions is a unique feature that is useful when dealing with projects that involve juggling between many tabs. Essentially, tab sessions lets you save the current state of the tabs. You can close your workspace, switch to a different branch, and instantly reload your previously opened files. You'll no longer need to work with opening and closing multiple files.

\n

To use tab sessions, select Save Tab Sessions from the tab button menu. Give it a unique name. When you're ready to restore your tab sessions, just select Load Tab Sessions.

\n

If you find that you've got too many tab sessions defined, you can always choose to delete them from the same tab menu.

\n\n
" + "filename": "setting_up_mysql", + "mtime": 1416491265000, + "pageTitle": "MySQL", + "contents": "

MySQL

\n

MySQL is the world's most widely used open source relational database management system (RDBMS) that runs as a server providing multi-user access to a number of databases.

\n

MySQL's most common features

\n
    \n
  • A broad subset of ANSI SQL 99, as well as extensions
    • \n
  • Cross-platform support
    • \n
  • Stored procedures
    • \n
  • Triggers
    • \n
  • Cursors
    • \n
  • Updatable Views
    • \n
  • Information schema
    • \n
  • Many more
    • \n
\n

Using MySQL with Cloud9

\n

This article explains our first iteration of MySQL support in Cloud9. It makes it super easy to install, start and stop a MySQL instance right in your workspace. The nice thing is that every workspace will run a separate database so your projects will never interfere with each other. You can control MySQL with the mysql-ctl command line tool run from the terminal:

\n
# start MySQL. Will create an empty database on first start\n$ mysql-ctl start\n\n# stop MySQL\n$ mysql-ctl stop\n\n# run the MySQL interactive shell\n$ mysql-ctl cli
\n

You can then connect to the database with following parameters:

\n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
Option\n Value\n Comment\n
Hostname$IPThe same local IP as the application you run on Cloud9
Port3306The default MySQL port number
User$C9_USERYour Cloud9 user name
Password-No password since you can only access the DB from within the workspace
Databasec9The database name
\n

Importing data into your database

\n

To import existing data into your database run following commands:

\n
mysql-ctl cli
\n

You are now in the MySQL environment and can start the import:

\n
mysql> use c9\nmysql> source PATH_TO_SQL_FILE.sql
\n

To verify that everything got imported run:

\n
mysql> show tables;
\n

Note:

MySQL socket file can be found in ~/lib/mysql/socket/mysql.sock\n\n
\n\n
" }, { - "filename": "status_bar", - "mtime": 1412172002000, - "pageTitle": "Status Bar", - "contents": "\n

Status Bar

\n

Note:

this feature is deprecated\n\n
\n

The status bar is designed to provide you with all sorts of information about your code--and additional functionality--without getting in the way of the IDE. It's quite tiny, and quite powerful, like a weight-lifting squirrel.

\n

You can find the status bar in the lower-right corner of the editor: \"The. Keep in mind that the status bar is transparent, so it's able to camoflauge well with light or dark themes.

\n

There's three pieces of crucial information available at all times: your current row, your current column, and, if you're highlighting characters, the status bar displays the number of bytes currently selected. If you're using Vim Mode, the status bar also tells you if you're in INSERT mode.

\n

If you click on the status bar, it expands into a menu that provides a smaller set of the full IDE preferences. These options only deal with the IDE editor:

\n
\n \n \n \n \n \n \n \n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
Preference NameDescription
Show InvisiblesShows invisibles characters in the editor, like tabs and line breaks
Wraps LinesWraps lines according to the line margin defined, or your browser's window. Otherwise, lines run off the current viewport.
Code FoldingWhen enabled, allows you to show or hide "blocks" of code
Full Line SelectionWhen highlighting lines, this option will highlight all ending whitespace, until the end of the editor window
Highlight Active LinePresents a darker shade in the code editor to indicate which line you're currently on
Show Indent GuidesShows the indent guides in the editor, letting you see your code's nestings
Show GutterShows the gutter in the editor, which indicates line numbers, warnings, and errors
Highlight Selected WordIf you highlight a word, this highlights all matching words in the editor
Auto-pair Quotes, Brackets, etc.When enabled, typing ", (, or [ will actually make two characters appear. In addition, whenever you highlight a word and type one of these characters, it is surrounded by that character (e.g. words becomes "words")
Auto-hide Horizontal Scrollbarhen this is enabled, this will hide the horizontal scroll bar in the editor. Note that this has no effect in Mac OS X 10.7 (Lion) and above, since all scrollbars, by default, auto-hide.
Font SizeChanges the font size of the code in the editor
Show Print MarginShows (and defines) the number of characters possible in line, before it wraps
Soft TabsIndicates how many spaces a single tab represents
Mouse Scroll SpeedDefines the speed of the mouse scrolls
\n
\n
" + "filename": "setting_up_phpmyadmin", + "mtime": 1416497235000, + "pageTitle": "PHPMyAdmin", + "contents": "

PHPMyAdmin

\n

PHPMyAdmin provides an easy to use web interface to manage your MySQL database/s

\n

PHPMyAdmin's most common features

\n
    \n
  • Import data from CSV and SQL
    • \n
  • Export data to various formats: CSV, SQL, XML, PDF, Word, Excel, LaTeX and others
    • \n
  • Creating PDF graphics of the database layout
    • \n
  • Creating complex queries using Query-by-Example (QBE)
    • \n
  • Searching globally in a database or a subset of it
    • \n
  • Transforming stored data into any format using a set of predefined functions, like displaying BLOB-data as image or download-link
    • \n
  • Live charts to monitor MySQL server activity like connections, processes, CPU/Memory usage, etc.
    • \n
  • Many more
    • \n
\n

Using PHPMyAdmin with Cloud9

\n

This article explains our first iteration of PHPMyAdmin support in Cloud9. It makes it super easy to install a PHPMyAdmin instance right in your workspace. Each workspace runs it's own Database and copy of PHPMyAdmin.

\n
# Install PHPMyAdmin\n$ phpmyadmin-ctl install
\n

After the installation is complete you'll be given a link to access PHPMyAdmin. If you'd like further help using the software please consult the official PHPMyAdmin docs.

\n\n
" }, { - "filename": "setting_up_mysql", - "mtime": 1412172002000, - "pageTitle": "MySQL", - "contents": "

MySQL

\n

MySQL is the world's most widely used open source relational database management system (RDBMS) that runs as a server providing multi-user access to a number of databases.

\n

MySQL's most common features

\n
    \n
  • A broad subset of ANSI SQL 99, as well as extensions
    • \n
  • Cross-platform support
    • \n
  • Stored procedures
    • \n
  • Triggers
    • \n
  • Cursors
    • \n
  • Updatable Views
    • \n
  • Information schema
    • \n
  • Many more
    • \n
\n

Using MySQL with Cloud9

\n

This article explains our first iteration of MySQL support in Cloud9. It makes it super easy to install, start and stop a MySQL instance right in your workspace. The nice thing is that every workspace will run a separate database so your projects will never interfere with each other. You can control MySQL with the mysql-ctl command line tool run from the terminal:

\n
# start MySQL. Will create an empty database on first start\n$ mysql-ctl start\n\n# stop MySQL\n$ mysql-ctl stop\n\n# run the MySQL interactive shell\n$ mysql-ctl cli
\n

You can then connect to the database with following parameters:

\n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
Option\n Value\n Comment\n
Hostname$IPThe same local IP as the application you run on Cloud9
Port3306The default MySQL port number
User$C9_USERYour Cloud9 user name
Password-No password since you can only access the DB from within the workspace
Databasec9The database name
\n

Importing data into your database

\n

To import existing data into your database run following commands:

\n
mysql-ctl cli
\n

You are now in the MySQL environment and can start the import:

\n
mysql> use c9\nmysql> source PATH_TO_SQL_FILE.sql
\n

To verify that everything got imported run:

\n
mysql> show tables;
\n

Note:

MySQL socket file can be found in ~/lib/mysql/socket/mysql.sock\n\n
\n\n
" + "filename": "setting_up_redis", + "mtime": 1416491265000, + "pageTitle": "Redis", + "contents": "

Redis

\n

Running

\n

Cloud9 workspaces come with redis pre-installed.

\n

Start the server:

\n
sudo service redis-server start
\n

Connect with the client:

\n
./redis-cli
\n

Drivers

\n

See http://redis.io/clients for drivers.

\n\n
" + }, + { + "filename": "setting_up_postgresql", + "mtime": 1416491265000, + "pageTitle": "PostgreSQL", + "contents": "

PostgreSQL

\n

Installing PostgreSQL on a Cloud9 workspace

\n

PostgreSQL comes preinstalled on every Cloud9 workspace, yay.

\n

Start the PostgreSQL service

\n
$ sudo service postgresql start
\n

Set the "postgres" user password

\n
$ sudo sudo -u postgres psql                                                                                  \npsql (9.3.4, server 9.3.5)\nType \"help\" for help.\n\npostgres=# \\password\nEnter new password: \nEnter it again: \npostgres=# \\q
\n

Connect to the service

\n
$ sudo sudo -u postgres psql
\n

Create a PostgreSQL database

\n

Make sure you have logged into the PostgreSQL terminal and then you can just run:

\n
$ sudo sudo -u postgres psql                                                                                  \npostgres=# create database \"groceries\";
\n

List all databases

\n
$ sudo sudo -u postgres psql                                                                                  \npostgres=# \\list
\n\n
" + }, + { + "filename": "setting_up_sqlite3", + "mtime": 1416491265000, + "pageTitle": "SQLite", + "contents": "

SQLite

\n

SQLite is a software library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine. SQLite is the most widely deployed SQL database engine in the world. The source code for SQLite is in the public domain.

\n

Note:

SQLite supports full text search and ACID transactions (atomic, consistent, isolated, and durable)\nWith its simplicity and zero-configuration, SQLite is a popular choice for new applications.\n\n
\n

Getting started

\n

You can open the terminal and create a database in a file db_test.db as follows:

\n

\"Screenshot

\n

Try yourself

\n
$ sqlite3 db_test.db\nSQLite version 3.6.20\nEnter \".help\" for instructions\nEnter SQL statements terminated with a \";\"\nsqlite> create table tbl1(one varchar(10), two smallint);\nsqlite> insert into tbl1 values('hello!',10);\nsqlite> insert into tbl1 values('goodbye', 20);\nsqlite> select * from tbl1;\nhello!|10\ngoodbye|20\nsqlite> CREATE TABLE tbl2 (\n   ...>   f1 varchar(30) primary key,\n   ...>   f2 text,\n   ...>   f3 real\n   ...> );\nsqlite> .exit
\n

To get to know sqlite commands, use the command: .help.

\n

To exit sqlite, use the command: .exit.

\n

Drivers

\n

SQLite has drivers for all supported runtimes.

\n

Following are the most commonly used drivers:

\n

Node.JS apps

\n

node-sqlite

\n

Rails apps

\n

In your Gemfile, include the line:

\n
gem 'sqlite3'
\n

and in configs/database.yml, make sure you use:

\n
adapter: sqlite3\ndatabase: db/development.db
\n\n
" }, { "filename": "common_errors", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Common errors", "contents": "

Common errors

\n

Sometimes you run into issues when you run your project. Here you will find the most common issues and how to solve them.

\n

Address in use or similar

\n

The most common reason for an error thrown by your app stating that a port or address is in use is the fact that some process is already running/listening on that port/address. You need to take a look for those and kill the processes conflicting with your app:

\n
// Find the process\nlsof -i tcp:$PORT
\n

If any relevant process is running you will get a list looking like this:

\n
COMMAND PID   USER   FD   TYPE   DEVICE SIZE/OFF NODE NAME\napache2 699 ubuntu    4u  IPv6 83213152      0t0  TCP *:http-alt (LISTEN)
\n

You now can kill that proccess. Make sure you replace PID with the ID of the process.

\n
// Kill the process\nkill -9 PID
\n

For the console wizards:

\n
kill -9 $(lsof -i:$PORT -t)
\n\n
" }, - { - "filename": "setting_up_mongodb", - "mtime": 1412172002000, - "pageTitle": "MongoDB", - "contents": "

MongoDB

\n

MongoDB is a scalable, high-performance, open source NoSQL database.

\n

MongoDB's most common features

\n
    \n

  • Document-Oriented Storage
    \nJSON-style documents with dynamic schemas offer simplicity and power.

    \n
    • \n

  • Full Index Support
    \nIndex on any attribute, just like you're used to.

    \n
    • \n

  • Querying
    \nRich, document-based queries.

    \n
    • \n
\n

In addition, MongoDB has many scalability features such as:

\n

Replication, Auto-sharding, Map/Reduce and GridFS

\n

Running MongoDB on a Cloud9 workspace

\n

MongoDB is preinstalled in your workspace. To run MongoDB, run the following below (passing the correct parameters to it). Mongodb data will be stored in the folder data.

\n
$ mkdir data\n$ echo 'mongod --bind_ip=$IP --dbpath=data --nojournal --rest \"$@\"' > mongod\n$ chmod a+x mongod
\n

You can start mongodb by running the mongod script on your project root:
\n$ ./mongod

\n

MongoDB parameters used:

\n

| Parameter | Description |\n| ------------------------------ | ----------------------------------------------------------------------------------------------- |\n| --dbpath=data | Because it defaults to /var/db which isn't accessible) |\n| --nojournal | Because mongodb usually pre-allocates 2 GB journal file (which exceeds Cloud9 disk space quota) |\n| --bind_ip=$IP | Because you can't bind to 0.0.0.0) |\n| --rest | Runs on default port 28017 |

\n

Drivers

\n

You should use the host $IP instead of localhost as your driver connection url.
\ne.g. in Node, it is: process.env.IP

\n

MongoDB has drivers for all supported runtimes. Following are the most commonly used drivers:

\n

Node.JS apps

\n

Mongoose
\nNode-Mongodb-Native

\n

Shell Access

\n

To access a shell prompt for the above MongoDB run the following.

\n
$ mongo
\n

Check out docs.mongodb.org for details on how to use the shell

\n\n
" - }, { "filename": "creating_coffeescript_app", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Create a CoffeeScript Project", "contents": "\n

Create a CoffeeScript Project

\n

For this tutorial, we'll show you how to create and run a CoffeeScript project, entirely within the Cloud9 IDE. To run any coffeescript project, you'll need to first make sure to install the coffeescript module via the Node Package Manager (npm). We're going to walk you through how to do that with a sample project.

\n

First, create a new project. Then, in the console, enter the following command:

\n
git clone git://github.com/fjakobs/cloud9-coffeescript-example.git
\n

This is a sample CoffeeScript application written by one of our developers. After cloning the project, you'll find three different files in the project tree: server.js, app.coffee, and README.md.

\n

The README.md file contains instructions to install coffee-script using npm. We've integrated Node Package Manager into Cloud9 IDE to enable users to install Node programs. Thus, from the Cloud9 IDE command line, type the following command to install the Coffeescript module:

\n
npm install coffee-script
\n

Next, let's have a look at the server.js file. The first line is the require() function, which is used to load the coffee-script module that you have just installed. On the second line, we declare the CoffeeScript file that contains your application. In the last line, we specify the port the server is listening to. When projects run within Cloud9 IDE, you must retrieve the port information using process.env.PORT.

\n

Now, let's look at what the CoffeeScript file does. It creates an HTTP server with a function that is called for each request. In the callback function, you create a response with a status code of 200 (indicating that the request was fulfilled successfully) and the message "Hello World". You use module.exports to enable the server.js file to use the code in the CoffeeScript file:

\n
http = require \"http\"\n\nmodule.exports = http.createServer((req, res) ->\n    res.writeHead 200, 'Content-Type': 'text/plain'\n    res.end 'Hello World\\n'
\n

Next, run the server.js file and open the URL indicated in the console:

\n

\"Messages

\n

The result is:

\n

\"The

\n

To stop your application, go back to the editor and click on the \"Icon button in the Menu Bar.

\n\n
" }, { "filename": "editing_wordpress_sites", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Editing Remote WordPress Websites via FTP", "contents": "\n

Editing Remote WordPress Websites via FTP

\n
\n\n
\n\n

Did you know that you can use Cloud9 IDE to work on your WordPress website? It's true, and incredibly easy. You can't edit your posts on WordPress using Cloud9, since they are stored in a database on your server. But you can edit pretty much every other aspect of your site.

\n

To start, you'll need to create a new FTP project. After that, enter your wp-content folder, find the theme you're using on your website, and start editing its style.

\n

Thanks to the preview button in the menu bar, you can also witness your changes as they happen, before committing them to your server.

\n\n
" }, - { - "filename": "setting_up_postgresql", - "mtime": 1412172002000, - "pageTitle": "PostgreSQL", - "contents": "

PostgreSQL

\n

Installing PostgreSQL on a Cloud9 workspace

\n

PostgreSQL comes preinstalled on every Cloud9 workspace, yay.

\n

Start the PostgreSQL service

\n
$ sudo service postgresql start
\n

Set the "postgres" user password

\n
$ sudo sudo -u postgres psql                                                                                  \npsql (9.3.4, server 9.3.5)\nType \"help\" for help.\n\npostgres=# \\password\nEnter new password: \nEnter it again: \npostgres=# \\q
\n

Connect to the service

\n
$ sudo sudo -u postgres psql
\n

Create a PostgreSQL database

\n

Make sure you have logged into the PostgreSQL terminal and then you can just run:

\n
$ sudo sudo -u postgres psql                                                                                  \npostgres=# create database \"groceries\";
\n

List all databases

\n
$ sudo sudo -u postgres psql                                                                                  \npostgres=# \\list
\n\n
" - }, { "filename": "installing_npm_modules", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Installing NPM Modules", "contents": "\n

Installing NPM Modules

\n

Since Cloud9 IDE is built on top of Node.js, we also leverage the module system NPM. In Cloud9, you can install any npm package either locally or globally. Note that due to security restrictions, modules installed globally can only be used in the project they were installed from. In other words, while you have access to any command line tools installed by the module, they are bound to the project, not your username. We run version 1.1.24 of npm.

\n

To demonstrate the power of NPM, we'll build and run a quick express server:

\n
    \n
  1. Launch the command line by hitting Shift-Escape. You can also go to View > Command Line if it's not visible.
    2. \n
  2. Type npm install express, and wait for the npm install process to complete.
    3. \n
  3. Create a new JavaScript file, and paste the following code:
    4. \n
\n
var express = require('express'),\n    app = express();\n\napp.use(express.logger());\n\napp.get('/', function(req, res){\n    res.send('Hello World');\n});\n\napp.listen(process.env.PORT);\nconsole.log('Express server started on port %s', process.env.PORT);
\n

To launch your express server, click on the \"The button in the menu bar.

\n\n
" }, { "filename": "installing_python_packages", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Installing Python Packages", "contents": "\n

Installing Python Packages

\n

Cloud9 supports the installation of Python packages for applications that need to go beyond the standard library set. Every workspace has version 0.6.10 of Python's easy_install package manager. For more information on this module, see the official easy_install documentation.

\n

Let's try installing a package. First, type the following in the console:

\n
easy_install markdown
\n

This installs the markdown Python package to your workspace. You won't see the package installed in the directory tree, because it's kept deep within your project's the Python libs.

\n

Next, create a new Python script, and add these lines of code:

\n
import markdown\n\nhtml = markdown.markdown(\"# HELLO THERE!\")\n\nprint html
\n

After clicking run, the console will correctly print out <h1>HELLO THERE!</h1>.

\n

You have access to all of the functionality easy_install provides you. For example, you can open up the Python REPL and type the following to see a list of your installed packages:

\n
>>> help('modules')
\n\n
" }, { - "filename": "setting_up_redis", - "mtime": 1416998221000, - "pageTitle": "Redis", - "contents": "

Redis

\n

Running

\n

Cloud9 workspaces come with redis pre-installed.

\n

Start the server:

\n
sudo service redis-server start
\n

Connect with the client:

\n
./redis-cli
\n

Drivers

\n

See http://redis.io/clients for drivers.

\n\n
" - }, - { - "filename": "setting_up_sqlite3", - "mtime": 1412172002000, - "pageTitle": "SQLite", - "contents": "

SQLite

\n

SQLite is a software library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine. SQLite is the most widely deployed SQL database engine in the world. The source code for SQLite is in the public domain.

\n

Note:

SQLite supports full text search and ACID transactions (atomic, consistent, isolated, and durable)\nWith its simplicity and zero-configuration, SQLite is a popular choice for new applications.\n\n
\n

Getting started

\n

You can open the terminal and create a database in a file db_test.db as follows:

\n

\"Screenshot

\n

Try yourself

\n
$ sqlite3 db_test.db\nSQLite version 3.6.20\nEnter \".help\" for instructions\nEnter SQL statements terminated with a \";\"\nsqlite> create table tbl1(one varchar(10), two smallint);\nsqlite> insert into tbl1 values('hello!',10);\nsqlite> insert into tbl1 values('goodbye', 20);\nsqlite> select * from tbl1;\nhello!|10\ngoodbye|20\nsqlite> CREATE TABLE tbl2 (\n   ...>   f1 varchar(30) primary key,\n   ...>   f2 text,\n   ...>   f3 real\n   ...> );\nsqlite> .exit
\n

To get to know sqlite commands, use the command: .help.

\n

To exit sqlite, use the command: .exit.

\n

Drivers

\n

SQLite has drivers for all supported runtimes.

\n

Following are the most commonly used drivers:

\n

Node.JS apps

\n

node-sqlite

\n

Rails apps

\n

In your Gemfile, include the line:

\n
gem 'sqlite3'
\n

and in configs/database.yml, make sure you use:

\n
adapter: sqlite3\ndatabase: db/development.db
\n\n
" + "filename": "installing_ruby_gems", + "mtime": 1416491265000, + "pageTitle": "Installing Ruby Gems", + "contents": "\n

Installing Ruby Gems

\n

Cloud9 supports the installation of Ruby gems in your workspace using the RubyGems package manager. The current installed RubyGems version is 1.3.7. For more information on the gem command, see the official RubyGems documentation.

\n

Let's try installing a gem. First, type the following in the console:

\n
gem install progressbar
\n

This installs the progressbar Ruby gem to your workspace. You won't see the gem installed in the directory tree, because it's kept deep within your project's the Ruby libs.

\n

Next, create a new Ruby script, and add these lines of code:

\n
require 'progressbar'\n\nbar = ProgressBar.new(\"Example progress\", 50)\ntotal = 0\nuntil total >= 100\n  sleep(rand(2)/2.0)\n  increment = (rand(6) + 3)\n  bar.inc(increment)\n  total += increment\nend
\n

After clicking run, the console will start printing out an ASCII progressbar.

\n

You have access to all of the functionality gem provides you. For example, you can open up the console and type gem query to see a list of your installed gems.

\n\n
" }, { "filename": "running_a_rails_app", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Running a Rails App", "contents": "

Running a Rails App

\n

Cloud9 IDE also supports the ability to run a Rails application. The rails command is only available on the terminal.

\n

To run a rails application:

\n
    \n
  1. Open the terminal and type gem install rails
    2. \n
  2. When done, type rails new example -d mysql
    3. \n
  3. Edit your database configuration in configs/database.yml
    4. \n
  4. Type rails s -b $IP -p $PORT
    5. \n
\n

That's it! Your rails app will now be running.

\n

Note:

http://<workspacename>-c9-<username>.c9.io should be running your application.\n\n
\n

Do not try to access the project through the IP address and port number rails returns to you--it won't work!

\n

Use MySQL in your rails app

\n
    \n

  1. Setup MySQl - note your DB connect parameters

    \n
    2. \n

  2. edit configs/database.yml

    \n
    3. \n
\n
development:\n  adapter: mysql2\n  encoding: utf8\n  database: c9\n  username: <%=ENV['C9_USER']%>\n  host: <%=ENV['IP']%>
\n\n
" }, { - "filename": "installing_ruby_gems", - "mtime": 1412172002000, - "pageTitle": "Installing Ruby Gems", - "contents": "\n

Installing Ruby Gems

\n

Cloud9 supports the installation of Ruby gems in your workspace using the RubyGems package manager. The current installed RubyGems version is 1.3.7. For more information on the gem command, see the official RubyGems documentation.

\n

Let's try installing a gem. First, type the following in the console:

\n
gem install progressbar
\n

This installs the progressbar Ruby gem to your workspace. You won't see the gem installed in the directory tree, because it's kept deep within your project's the Ruby libs.

\n

Next, create a new Ruby script, and add these lines of code:

\n
require 'progressbar'\n\nbar = ProgressBar.new(\"Example progress\", 50)\ntotal = 0\nuntil total >= 100\n  sleep(rand(2)/2.0)\n  increment = (rand(6) + 3)\n  bar.inc(increment)\n  total += increment\nend
\n

After clicking run, the console will start printing out an ASCII progressbar.

\n

You have access to all of the functionality gem provides you. For example, you can open up the console and type gem query to see a list of your installed gems.

\n\n
" + "filename": "running_and_debugging_code", + "mtime": 1416491265000, + "pageTitle": "Running and Debugging Your Code", + "contents": "

Running and Debugging Your Code

\n

Cloud9 IDE provides several ways to run and debug your code. We'll explore each of them in this section of the documentation.

\n

Note:

Currently, only Javascript/Node.js applications can make use of the debugger. You can also execute Javascript/Node.js, Python, Ruby, and Apache+PHP applications.\n\n
\n

The following information applies to all of the above programming languages.

\n

Running Code

\n

Running your code in Cloud9 is really easy. First, open the file you want to run. Usually, this file is going to be the main entry point to your app; for example, if you're creating a server, you'd want to run the file that actually instantiates that server.

\n

There are two ways to run your code: either through the Run Panel, or through the run button in the menu bar.

\n

Using the Run Panel

\n

Next, click on the Run button in the project bar. You'll notice immediately that your active file is already available to run. Just double-click on the file, and you'll launch your app.

\n

When you're ready to stop your app, click on the \"Icon button in the menu bar at any time.

\n

At the bottom of the run panel, you'll notice a few more options you can set. Filling these textboxes out creates a run scenario, which is like setting up some configurations for the way your code runs. These options are:

\n
    \n
  • Name the name of your run scenario
    • \n
  • File Path: the location of your running file in your project
    • \n
  • Runtime: defines how you want your code to be run. Typically, you'd set different runtime versions here.
    • \n
  • Cmd Line Args: allows you to provide any additional command line arguments you want to pass to your app
    • \n
\n

Of course, you can also save your run scenarios; just click on the add button at the top of the panel. When you're ready to run a scenario, click on its name in the Run panel list. To remove a run scenario, click on its name in the run panel list, and then click on the remove button.

\n

Using the Run Button

\n

The run button in the menu bar acts as a sort of short cut to the Run panel. When clicked, the button automatically runs the currently active file. If you have a list of run scenarios already defined, the run button also presents a list of those:

\n

\"Run

\n

Run in debug mode indicates that you want to run the current code through the debugger. Auto show & hide debug tools will reveal (or collapse) the debugging tools panel described below. You can also work with this presentation by going to View > Panels, and configuring the debugger there.

\n

Console Output

\n

Every time you run a project, the console expands to reveal output from your program. If you're launching a server, Cloud9 provides you with a URL to access the project. Otherwise, any statements sent by your application's print statements (like console.log() for Javascript, print for Python, or puts for Ruby) are also shown here. For example:
\"Console

\n

Debugging Your Code

\n

Setting up a project to debug is done in very much the same way as running your code. The only difference is that you must click on the run settings icon in the Run panel \"Run and select Run in debug mode. Similarly, you can select Run in debug mode from the run button.

\n

Initially, the only difference this will make is the expansion of the debugging toolbar to the right of the editor:
\"The

\n

This toolbar, however, grants you the following capabilities:

\n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
Toolbar IconDebugging FunctionDescription
\"DebuggingDebugging NavigationThis is a set of tools you can use to move around your code while debugging. You can step into, over, and out of your code, or simply press play to run the process until the next breakpoint.
\"IconCallstackThis is a structured list of information about the sequences of your code--basically, which functions are calling what, and where you are in the current process. It also stores local variables and function arguments, if present. You can use this feature to check how your code is running:
\"Callstack
\"IconInteractive ModeLets you evaluate a piece of code, such as expressions or the values and properties of variables. The text field allows you to type any code you want, in case you discover a way to fix you problem:\n\"Interactive
\"IconVariable InspectionThis shows all the related variables (including functions) that are present in the current context:\n\"Variable
\"IconBreakpoint ListAt any point during your coding or debugging session, you can click on the gutter to apply a breakpoint: \"Breakpoint. When debugging your code, the process pauses at your established breakpoints, so that you can inspect closely what's going on in a certain part of the code. You can click on the breakpoint list to view all the breakpoints in your workspace. If you click on the checkbox, you can enable or disable a breakpoint as well. You can also click on a breakpoint in the gutter to disable or enable it.
\n

While debugging, you also have the power of the live inspector. While hovering over a piece of code in the editor, you'll instantly get some floating text that describes the values of that variable, similar to Variable Inspection.
\"Live

\n\n
" }, { "filename": "running_wordpress_on_cloud9", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Running WordPress on Cloud9", "contents": "

Running WordPress on Cloud9

\n

WordPress is web software you can use to create websites or blogs.\nYou can develop and host WordPress websites entirely on Cloud9 IDE

\n

Creating a wordpress workspace

\n

Create a WordPress workspace from the WordPress template on your Cloud9 dashboard

\n

Note:

We will download, extract and configure WordPress for you.\n\n
\n

In order to run WordPress, you need a database to host your posts, articles, etc.

\n

You can use MySQL with our utility script mysql-ctl as explained in MySQL Setup

\n

Running the website

\n

To start MySQL server and create the required database, type in the terminal:

\n
mysql-ctl start
\n

Open index.php in your workspace root and click the Run button

\n

You can check the generated config for you In wp-config.php (you don't need to change anything there)

\n
define('DB_NAME', 'c9');\ndefine('DB_USER', getenv('C9_USER'));\ndefine('DB_PASSWORD', '');\ndefine('DB_HOST', getenv('IP'));\ndefine('WP_SITEURL', 'http://' . getenv('C9_PROJECT') . '.' . getenv('C9_USER') . '.c9.io');
\n\n
" }, { - "filename": "running_and_debugging_code", - "mtime": 1412172002000, - "pageTitle": "Running and Debugging Your Code", - "contents": "

Running and Debugging Your Code

\n

Cloud9 IDE provides several ways to run and debug your code. We'll explore each of them in this section of the documentation.

\n

Note:

Currently, only Javascript/Node.js applications can make use of the debugger. You can also execute Javascript/Node.js, Python, Ruby, and Apache+PHP applications.\n\n
\n

The following information applies to all of the above programming languages.

\n

Running Code

\n

Running your code in Cloud9 is really easy. First, open the file you want to run. Usually, this file is going to be the main entry point to your app; for example, if you're creating a server, you'd want to run the file that actually instantiates that server.

\n

There are two ways to run your code: either through the Run Panel, or through the run button in the menu bar.

\n

Using the Run Panel

\n

Next, click on the Run button in the project bar. You'll notice immediately that your active file is already available to run. Just double-click on the file, and you'll launch your app.

\n

When you're ready to stop your app, click on the \"Icon button in the menu bar at any time.

\n

At the bottom of the run panel, you'll notice a few more options you can set. Filling these textboxes out creates a run scenario, which is like setting up some configurations for the way your code runs. These options are:

\n
    \n
  • Name the name of your run scenario
    • \n
  • File Path: the location of your running file in your project
    • \n
  • Runtime: defines how you want your code to be run. Typically, you'd set different runtime versions here.
    • \n
  • Cmd Line Args: allows you to provide any additional command line arguments you want to pass to your app
    • \n
\n

Of course, you can also save your run scenarios; just click on the add button at the top of the panel. When you're ready to run a scenario, click on its name in the Run panel list. To remove a run scenario, click on its name in the run panel list, and then click on the remove button.

\n

Using the Run Button

\n

The run button in the menu bar acts as a sort of short cut to the Run panel. When clicked, the button automatically runs the currently active file. If you have a list of run scenarios already defined, the run button also presents a list of those:

\n

\"Run

\n

Run in debug mode indicates that you want to run the current code through the debugger. Auto show & hide debug tools will reveal (or collapse) the debugging tools panel described below. You can also work with this presentation by going to View > Panels, and configuring the debugger there.

\n

Console Output

\n

Every time you run a project, the console expands to reveal output from your program. If you're launching a server, Cloud9 provides you with a URL to access the project. Otherwise, any statements sent by your application's print statements (like console.log() for Javascript, print for Python, or puts for Ruby) are also shown here. For example:
\"Console

\n

Debugging Your Code

\n

Setting up a project to debug is done in very much the same way as running your code. The only difference is that you must click on the run settings icon in the Run panel \"Run and select Run in debug mode. Similarly, you can select Run in debug mode from the run button.

\n

Initially, the only difference this will make is the expansion of the debugging toolbar to the right of the editor:
\"The

\n

This toolbar, however, grants you the following capabilities:

\n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
Toolbar IconDebugging FunctionDescription
\"DebuggingDebugging NavigationThis is a set of tools you can use to move around your code while debugging. You can step into, over, and out of your code, or simply press play to run the process until the next breakpoint.
\"IconCallstackThis is a structured list of information about the sequences of your code--basically, which functions are calling what, and where you are in the current process. It also stores local variables and function arguments, if present. You can use this feature to check how your code is running:
\"Callstack
\"IconInteractive ModeLets you evaluate a piece of code, such as expressions or the values and properties of variables. The text field allows you to type any code you want, in case you discover a way to fix you problem:\n\"Interactive
\"IconVariable InspectionThis shows all the related variables (including functions) that are present in the current context:\n\"Variable
\"IconBreakpoint ListAt any point during your coding or debugging session, you can click on the gutter to apply a breakpoint: \"Breakpoint. When debugging your code, the process pauses at your established breakpoints, so that you can inspect closely what's going on in a certain part of the code. You can click on the breakpoint list to view all the breakpoints in your workspace. If you click on the checkbox, you can enable or disable a breakpoint as well. You can also click on a breakpoint in the gutter to disable or enable it.
\n

While debugging, you also have the power of the live inspector. While hovering over a piece of code in the editor, you'll instantly get some floating text that describes the values of that variable, similar to Variable Inspection.
\"Live

\n\n
" - }, - { - "filename": "writing_a_python_app", - "mtime": 1412172002000, - "pageTitle": "Writing a Python App", - "contents": "\n

Writing a Python App

\n

While using Cloud9 IDE, you have access to the Python runtime. Accessing the command is no different than the way you'd use Python on your computer; just open the command line and type python. Currently, we run version 2.6.6.

\n

To run a Python program that you've created, you can either:

\n
    \n
  • Open the command line and type python, followed by the name of your program; for example python hello_world.py
    • \n
  • Create a new run scenario, so that you can do things like pass in command line arguments
    • \n
\n

As a quick demonstration, open a new file, and paste this Python code into it:

\n
#!/usr/bin/python\n\nprint \"Hello World!\";
\n

When you hit the \"The button in the menu bar, the console will print out Hello World!.

\n

Note:

Currently, you can't debug Python applications, but we are working on adding this feature.
\n\n
" + "filename": "terminal_monitor", + "mtime": 1416491265000, + "pageTitle": "The Terminal Monitor", + "contents": "\n

The Terminal Monitor

\n

Many times your app returns errors which are hard to understand and even harder to resolve. This is where the Terminal Monitor comes in.\nThe following video gives a quick overview of the features and how the Terminal Monitor helps you write better apps.

\n\n\n

If you would like to propose additions or help which Terminal Monitor should provide, please send a message to support@c9.io

\n\n
" }, { "filename": "writing_a_go_app", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Writing a Go App", "contents": "

Writing a Go App

\n

Cloud9 IDE doesn't provide out-of-the-box support for the Go language, but with \na few quick steps you can set up Cloud9 to build and run apps in Go!

\n

Create a new workspace

\n

First, create a new Custom workspace and call it whatever you want:

\n

\"Create

\n

After your new workspace is created, click the "start editing" button. At the \nbottom of your workspace you will see the Terminal. If you prefer to have it\nfullscreen, you can launch a terminal tab by pressing Alt-T, or from the menu: \nView > Terminals > New Terminal.

\n

From the terminal you can install & setup everything on the underlying virtual \nenvironment that every workspace is provided with.

\n

Download Go

\n

When you first enter your Terminal, you will be in your workspace root folder, \nwhich is a number such as ~/562166. Make a note of this directory name, as \nyou'll need it later.

\n

Let's use your home directory to download the Go distribution; to get there, \nsimply enter the following in the Terminal:

\n
cd ..
\n

To download the Go distribution enter the following:

\n
wget https://go.googlecode.com/files/go1.1.1.linux-amd64.tar.gz
\n

Note:

at the time of writing the latest version was 1.1.1, but you might want to \nuse a new version if it has become available. \n\n
\n

After the download is complete, extract the archive:

\n
tar -xzf go1.1.1.linux-amd64.tar.gz
\n

Once the extraction is done, you will notice a new go directory in your home \ndirectory. Feel free to delete the archive file you downloaded.

\n

Set up your environment

\n

The last step is to configure the environment so it can see the Go distribution \nas well as our workspace Go files. To do this, edit your bash configuration \nin the Terminal using vim (or emacs, nano, any simple editor will do):

\n
vim ~/.bashrc
\n

Add the following lines to your .bashrc file:

\n
# setup go configuration \nexport GOROOT=$HOME/go \nexport PATH=$PATH:$GOROOT/bin \n\n# setup workspace t\nexport GOPATH=$HOME/562166 \nexport PATH=$PATH:$GOPATH/bin
\n

Update the GOPATH line above to use the workspace directory you noted earlier \n(so don't use $HOME/562166).

\n

After you save your .bashrc file, load the new settings:

\n
source ~/.bashrc
\n

That's it! You should be good to Go (pun intended).

\n

Note:

Thanks to Scotty Moon for writing an article about Go on Cloud9 IDE\nand letting us use it for documentation!
\n\n
" }, { - "filename": "terminal_monitor", - "mtime": 1412172002000, - "pageTitle": "The Terminal Monitor", - "contents": "\n

The Terminal Monitor

\n

Many times your app returns errors which are hard to understand and even harder to resolve. This is where the Terminal Monitor comes in.\nThe following video gives a quick overview of the features and how the Terminal Monitor helps you write better apps.

\n\n\n

If you would like to propose additions or help which Terminal Monitor should provide, please send a message to support@c9.io

\n\n
" + "filename": "writing_a_php_app", + "mtime": 1416491265000, + "pageTitle": "Writing a PHP App", + "contents": "

Writing a PHP App

\n

With Cloud9 IDE, you can run your PHP pages, without relying on a third-party system like Apache hosting. We run PHP version 5.3.3.

\n

You can choose to run PHP scripts via the command line, by typing php, followed by the name of your PHP file. However, this is not a very common use case. Most likely, you'll be running your own server and hosting PHP files.

\n

Here's a simple demonstration. First, create a PHP file called hello_world.php, and paste this code into it:

\n
<html>\n  <head>\n   <title>PHP Test</title>\n  </head>\n  <body>\n   <?php echo '<p>Hello World</p>'; ?> \n  </body>\n</html>
\n

Next, open the Run & Debug panel, at the left of the IDE. From the Runtime dropdown, select Apache+PHP. Then, click on the \"The button in the top menu bar.

\n

The console should now spit out a message about how your Apache server is running, something similar to this:

\n
Running Apache Process\nTip: you can access long running processes, like a server, at 'http://php_hello.gjtorikian.c9.io'.
\n

Clicking on that link gets you to your PHP page. For a more in-depth workflow, see the article on running WordPress entirely on Cloud9.

\n

Modifying php.ini

\n

You can configure your PHP installation by editing the php.ini located in the /home/ubuntu/workspace directory. Please note: in some cases php.ini is located somewhere else. Just create a simple PHP file running phpinfo() to find out where to look for php.ini.

\n

Make sure to restart Apache after you have applied your changes

\n
apachectl restart
\n

Note:

Currently, you can't debug PHP applications yet, but we are working on adding this feature.\n
\n\n
" + }, + { + "filename": "writing_a_python_app", + "mtime": 1416491265000, + "pageTitle": "Writing a Python App", + "contents": "\n

Writing a Python App

\n

While using Cloud9 IDE, you have access to the Python runtime. Accessing the command is no different than the way you'd use Python on your computer; just open the command line and type python. Currently, we run version 2.6.6.

\n

To run a Python program that you've created, you can either:

\n
    \n
  • Open the command line and type python, followed by the name of your program; for example python hello_world.py
    • \n
  • Create a new run scenario, so that you can do things like pass in command line arguments
    • \n
\n

As a quick demonstration, open a new file, and paste this Python code into it:

\n
#!/usr/bin/python\n\nprint \"Hello World!\";
\n

When you hit the \"The button in the menu bar, the console will print out Hello World!.

\n

Note:

Currently, you can't debug Python applications, but we are working on adding this feature.
\n\n
" }, { "filename": "writing_a_ruby_app", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Writing a Ruby App", "contents": "

Writing a Ruby App

\n

While using Cloud9 IDE, you have access to the Ruby runtime. Accessing the command is no different than the way you'd use Ruby on your computer; just open the command line and type ruby. Currently, the default version is 1.9.3.

\n

To run a Ruby program that you've created, you can either:

\n
    \n
  • Open the command line and type ruby, followed by the name of your program; for example ruby hello_world.rb
    • \n
  • Create a new run scenario, so that you can do things like pass in command line arguments
    • \n
\n

As a quick demonstration, open a new file, and paste this Ruby code into it:

\n
#!/usr/bin/ruby\n\nputs 'Hello world'
\n

When you hit the \"The button in the menu bar, the console will print out Hello world.

\n

Note:

Currently, you can't debug Ruby applications, but we are working on adding this feature.\n\n
\n

RVM Support

\n

We have rudimentary support for rvm, that allows you only to switch between versions 1.8.7 and 1.9.3. We don't support rvm per-project or global gemsets.

\n

To use rvm, open the terminal and type:

\n
# to switch to version 1.8.7\nrvm use 1.8\nrvm use 1.8.7 \n\n# to switch to version 1.9.3\nrvm use 1.9\nrvm use 1.9.3
\n

However, if you like, you can install the "real" rvm by executing the following command in the terminal:

\n
curl -L https://get.rvm.io | bash -s stable
\n

To grab the latest rvm AND the latest Ruby version, type:

\n
curl -L https://get.rvm.io | bash -s stable --ruby
\n\n
" }, { "filename": "creating_new_workspace", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Creating a New Workspace", "contents": "

Creating a New Workspace

\n

Cloud9 supports three types of workspaces:

\n
    \n
  1. Hosted
    2. \n
  2. FTP
    3. \n
  3. SSH
    4. \n
\n

In this article, we'll walk you through the creation of a new workspace and describe the choices you encounter.

\n

The first step for creating a new workspace is click the "CREATE NEW WORKSPACE" button in your Dashboard:

\n

\"New

\n

At this point, you'll encounter two choices: Create a new workspace and Clone from URL. Here's what they mean:

\n
    \n
  • Create a New Workspace allows you to create any of the previously mentioned types of workspaces (hosted, FTP, or SSH).
    • \n
  • Clone from URL allows you to instantly create a workspace from a repository, like GitHub or Bitbucket, using its URL. We'll explain more about this in the section below.
    • \n
\n

Create a New Workspace

\n

After clicking on Create a new workspace, you're taken to the screen below:

\n

\"Options

\n

First, let's enter a workspace name.\nDepending on whether you have a Free of Premium account, you can choose to make it either Public (open to anyone with the URL), or Private (only accessible to you and people you share it with).

\n

After this, choose the type of workspace you want to create:

\n
    \n
  • Hosted: This is a regular Cloud9 workspace, powered by a full Ubuntu environment. You even have sudo powers! This is the best choice for most people, and we've included some more info about it below.
    • \n
  • FTP allows you to upload your files directly to an FTP server that you have access to
    • \n
  • SSH, also called the "bring your own server" feature, lets you log into a server you own and run Cloud9 from there
    • \n
\n

Make a choice for the type of workspace and press Create. That's it! You can now see your new workspace in the dashboard:

\n

\"New

\n

Now, just click Start Editing to get started!

\n

Hosted workspaces

\n

Choose this workspace type to start from scratch with a 'Custom' workspace, or simply pick a pre-configured environment like Node.js, WordPress, or Python/Django, and immediately start developing your app.\nThis way you don't need to spend valuable development time on system setup and maintenance, as we maintain it, and you control it.

\n

\"Options

\n

As it's powered by a full Linux Ubuntu environment, hosted workspaces allow you to install any package (sudo apt-get install package), run git commands from the console to push your changes to a GitHub repo or a Bitbucket git repo, etcetera.

\n

Cloning from a URL

\n

The second option for creating a new workspace is to clone one from URL. The URL would be, for example, the URL of a GitHub workspace.

\n

In fact, let's clone a workspace. When you click on Clone from URL, you're taken to this screen:

\n

\"Options

\n

Paste the following GitHub URL in the textbox labeled Source URL: https://github.com/mattpardee/geekdots

\n

If you have a premium account, you can choose who has access to your workspace. For regular users, the new workspace will be public.

\n

Now, check out the workspace. It will be created under My Workspaces. You can now start editing it!

\n

Deleting a Workspace

\n

Now that you know how to create a workspace, you should also learn how to delete one. Look at the far right side of your dashboard:

\n

\"Delete

\n

Clicking on the Delete button prompts the IDE to ask for confirmation:
\"Confirmation

\n

This is your last chance to change your mind. Once you have typed delete in the textbox and pressed the red button, your workspace will be gone forever from Cloud9. If you are sure you want to delete your workspace, go ahead and press the red button. Of course, if your workspace is hosted elsewhere, like on another git or FTP server, it still exists in those repositories.

\n\n
" }, - { - "filename": "ftp_workspaces", - "mtime": 1412172002000, - "pageTitle": "Setting up an FTP project", - "contents": "\n

Setting up an FTP project

\n
\n\n
\n\n

In this article, we'll show you how to set up an FTP project.

\n

Note:

Currently, Cloud9 IDE only supports passive FTP. Active FTP, SFTP and FTPS are not yet supported. For SSH connections, consider creating an SSH workspace.\n\n
\n

To create an FTP project, go to the Dashboard and click on the \"Project next to MY PROJECTS. Choose the option to Create a new project (see "Creating a New Project" if you need to review the steps to create a new project):
\"New

\n

In the pop-up window that appears, select FTP for the project type:

\n

\"FTP

\n

Let's review the options available for your FTP project:

\n
    \n
  • Hostname: the domain name or IP address of the machine running your FTP server.
    • \n
  • Username: your username for the FTP server.
    • \n
  • Password: your password for the FTP server.
    • \n
  • Initial path: this is an optional parameter. You can set it as an absolute (starts with /) path. Otherwise, it'll be set to a relative path, and Cloud9 assumes that you want to start from the folder your FTP server leaves you after login (home or default folder).
    • \n
\n

Warning:

Be careful not to put an initial path that leaves you in a location where you don't have write privileges as that could cause problems.\n\n
\n

Fill in your FTP details and click the Login Test to verify that the settings are correct. If the test succeeds, go ahead and click Create to create your FTP project. You'll then see your project in the Dashboard under My Projects:

\n

\"New

\n

When your new FTP project is selected, you will see three buttons: Start Editing, FTP settings, and Delete (on the far right). FTP settings gives you access to the settings you just filled in, as well as the login test. This is useful to use in case your login credentials have changed.

\n

To get started with your FTP project, click on the Start Editing button. You'll be taken to the editor. Under Project Files, you should see the files from the FTP server in the directory you selected (either your home/default folder or the location indicated by the Initial Path, if you set it). The editor for FTP projects works the same as in other projects: you can create and edit your files in the usual way. The main difference is the FTP log at the bottom of the page (where the console is usually located for other non-FTP projects).

\n

The FTP log displays output related to the interaction with the FTP server. The screenshot below, for example, shows what happens when we create a new file called TestFile.txt. The file is created in the FTP server and when I write to it, the contents are transferred.

\n

\"Demonstrating

\n

Note:

In an FTP project, all files are stored on your FTP server; Cloud9 only stores the FTP settings. Please keep this in mind. Cloud9 IDE does not keep any copies of your files, so make sure you back them up properly. Any changes you make to these files in Cloud9 are automatically reflected on the live web server.
\n\n
" - }, { "filename": "writing_nodejs_hello_world", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Writing and Running a Node.js Program", "contents": "

Writing and Running a Node.js Program

\n

Cloud9 IDE was built on top of the Node.js platform, and as such, you have full access to the node runtime. Currently, we support running both version v0.6.x and v0.8.x.

\n

In this section, we'll walk you through the creation of a simple Hello World program. To get started, you'll first need to create a (GitHub or Mercurial) project. If you need a refresher on how to do this, please refer to Creating a New Workspace.

\n

A Simple Node.js HTTP Server

\n

Once you're in Cloud9, create a new file called server.js. Type the following code in the file:

\n
var http = require('http');\nhttp.createServer(function (req, res) {\n    res.writeHead(200, {'Content-Type': 'text/plain'});\n    res.end('Hello World\\n');\n}).listen(process.env.PORT, process.env.IP);
\n

This is a Node.js HTTP server. It returns a simple "Hello World" page every time you access the page. In short, you are creating an HTTP server with a callback function that is called for each request.

\n

In the callback function, you create a response with a status code of 200 (indicating that the request was fulfilled successfully) and the message "Hello World". Finally, you specify which port and IP address the server runs on. When Cloud9 IDE runs servers, you set and retrieve the IP address and port number with the process.env.IP and process.env.PORT variables.

\n

When you hit the \"The button in the menu bar, the console will print out the following message:
\"Console

\n

To see your application in action, click on the link created for your project. You should see your "Hello World" application open up in a new browser tab:
\"Node.js.

\n

NVM Support

\n

We have rudimentary support for nvm, that allows you only to switch between Node.js versions 0.6.21 and 0.8.x.

\n

To use nvm, open the terminal and type:

\n
# to switch to version 0.6.21\nnvm use v0.67 \n\n# to switch to the latest 0.8.x\nnvm use v0.8
\n\n
" }, { - "filename": "writing_a_php_app", - "mtime": 1412172002000, - "pageTitle": "Writing a PHP App", - "contents": "

Writing a PHP App

\n

With Cloud9 IDE, you can run your PHP pages, without relying on a third-party system like Apache hosting. We run PHP version 5.3.3.

\n

You can choose to run PHP scripts via the command line, by typing php, followed by the name of your PHP file. However, this is not a very common use case. Most likely, you'll be running your own server and hosting PHP files.

\n

Here's a simple demonstration. First, create a PHP file called hello_world.php, and paste this code into it:

\n
<html>\n  <head>\n   <title>PHP Test</title>\n  </head>\n  <body>\n   <?php echo '<p>Hello World</p>'; ?> \n  </body>\n</html>
\n

Next, open the Run & Debug panel, at the left of the IDE. From the Runtime dropdown, select Apache+PHP. Then, click on the \"The button in the top menu bar.

\n

The console should now spit out a message about how your Apache server is running, something similar to this:

\n
Running Apache Process\nTip: you can access long running processes, like a server, at 'http://php_hello.gjtorikian.c9.io'.
\n

Clicking on that link gets you to your PHP page. For a more in-depth workflow, see the article on running WordPress entirely on Cloud9.

\n

Modifying php.ini

\n

You can configure your PHP installation by editing the php.ini located in the /home/ubuntu/workspace directory. Please note: in some cases php.ini is located somewhere else. Just create a simple PHP file running phpinfo() to find out where to look for php.ini.

\n

Make sure to restart Apache after you have applied your changes

\n
apachectl restart
\n

Note:

Currently, you can't debug PHP applications yet, but we are working on adding this feature.\n
\n\n
" - }, - { - "filename": "setting_up_bitbucket_workspace", - "mtime": 1412172002000, - "pageTitle": "Setting Up a Bitbucket Workspace", - "contents": "

Setting Up a Bitbucket Workspace

\n

Bitbucket is a code-hosting services that offers both git and mercurial support. Projects can be listed as private or public, absolutely free. For more information on Bitbucket, visit https://bitbucket.org.

\n

We have integrated Bitbucket into the IDE to enable you to easily work on your public and private repositories. The following article explains how you can activate your Bitbucket account in Cloud9 IDE.

\n

Bitbucket Activation

\n

You can manage your add-on services from your user profile that you can find in the dashboard. When you have just signed in, click Your Account on the top of the left-side panel. Here, you can change the settings of your account. At the bottom, you'll see a list of add-on services that are integrated into Cloud9 IDE. Click activate on the Bitbucket button:

\n

\"Add-on

\n

A new window will pop-up on your screen. This window asks you to give authorization permission for the Cloud9 IDE application to interact in various ways with Bitbucket:

\n

\"Bitbucket

\n

To finalize the activation, click on Allow. Next, you're redirected to your account page, where you'll notice that your Bitbucket account is activated. You can deactivate Bitbucket by simply clicking deactivate, which may be useful when you want to link your Bitbucket account to another Cloud9 account.

\n

Now that you have activated Bitbucket, you can start to create and manage your projects!

\n

Managing Projects

\n

There are several ways to manage Bitbucket projects in Cloud9 IDE:

\n
    \n
  • By creating a new git or mercurial project and pushing it to Bitbucket
    • \n
  • By cloning a Bitbucket project from a URL
    • \n
  • By bringing in a Bitbucket project manually
    • \n
\n

Creating a New Git Project

\n

New projects are created from the dashboard. In the left-side panel, click on the \"Project to add a new project:

\n

\"New

\n

A new window will pop-up in which you can change your settings to your preferences:

\n
    \n
  • Fill in your preferred project name in the text field
    • \n
  • Choose who will have access to the project (a feature for Premium customers)
    • \n
  • Select your project type (git, mercurial, or FTP)
    • \n
  • Choose a development server (a feature for Premium customers)
    • \n
\n

\"New

\n

After you click CREATE, the project is listed in your dashboard. Select the project to see its Project Profile, where you can start editing: \"Start

\n

There are a couple of things you should do first, before you can use all of git's power. First, you'll want to add a remote to the project. From the Cloud9 IDE command line, you can execute the following commands:

\n
git remote add [remote name] [remote url]
\n

remote url is the location of the project on Bitbucket; for example 'origin git@bitbucket.org:username/repository_name.git'. You'll have to create a Bitbucket project first in order to generate this URL. Adding a remote URL lets you freely push and pull your project.

\n

Next, create a few new files inside your project. By default, you should already have a README.md. You can add these files to git with the following command:

\n
git add [file1, file2, file3, ...]
\n

Finally, create a commit that you can push to your remote:

\n
git commit -m 'added new files'
\n

Don't forget to push this commit out to Bitbucket:

\n
git push [remote name] master
\n

Ta-da! Your project is developed on Cloud9, and stored in Bitbucket.

\n

Cloning Projects from a URL

\n

You can also create a project in Cloud9 IDE by cloning it from a URL. Once again, click on the \"Project, and select Clone from URL. A new window pops up, asking you:

\n
    \n
  • to enter a Source URL
    • \n
  • to choose who will have access to the project (Premium feature)
    • \n
  • to choose a development server (Premium feature)
    • \n
\n

\"Clone

\n

You can find an examples of a Bitbucket URL on any of their repo description pages:

\n

\"Bitbucket

\n

Paste the URL in the source field and click CHECKOUT. In the left-side panel, you'll see the project and its status turn into "Cloning in Progress". When this process is completed you can open the project and start editing it, just like any other project.

\n

Clone Projects Already On Bitbucket

\n

When you provide Cloud9 IDE with your Bitbucket credentials, it provides a list of projects you haven't yet imported into the editor:

\n

\"Bitbucket

\n

From this list, clicking on a project and selecting CLONE TO EDIT brings the repo into the IDE, just as if you cloned it from a URL.

\n\n
" + "filename": "ftp_workspaces", + "mtime": 1416491265000, + "pageTitle": "Setting up an FTP project", + "contents": "\n

Setting up an FTP project

\n
\n\n
\n\n

In this article, we'll show you how to set up an FTP project.

\n

Note:

Currently, Cloud9 IDE only supports passive FTP. Active FTP, SFTP and FTPS are not yet supported. For SSH connections, consider creating an SSH workspace.\n\n
\n

To create an FTP project, go to the Dashboard and click on the \"Project next to MY PROJECTS. Choose the option to Create a new project (see "Creating a New Project" if you need to review the steps to create a new project):
\"New

\n

In the pop-up window that appears, select FTP for the project type:

\n

\"FTP

\n

Let's review the options available for your FTP project:

\n
    \n
  • Hostname: the domain name or IP address of the machine running your FTP server.
    • \n
  • Username: your username for the FTP server.
    • \n
  • Password: your password for the FTP server.
    • \n
  • Initial path: this is an optional parameter. You can set it as an absolute (starts with /) path. Otherwise, it'll be set to a relative path, and Cloud9 assumes that you want to start from the folder your FTP server leaves you after login (home or default folder).
    • \n
\n

Warning:

Be careful not to put an initial path that leaves you in a location where you don't have write privileges as that could cause problems.\n\n
\n

Fill in your FTP details and click the Login Test to verify that the settings are correct. If the test succeeds, go ahead and click Create to create your FTP project. You'll then see your project in the Dashboard under My Projects:

\n

\"New

\n

When your new FTP project is selected, you will see three buttons: Start Editing, FTP settings, and Delete (on the far right). FTP settings gives you access to the settings you just filled in, as well as the login test. This is useful to use in case your login credentials have changed.

\n

To get started with your FTP project, click on the Start Editing button. You'll be taken to the editor. Under Project Files, you should see the files from the FTP server in the directory you selected (either your home/default folder or the location indicated by the Initial Path, if you set it). The editor for FTP projects works the same as in other projects: you can create and edit your files in the usual way. The main difference is the FTP log at the bottom of the page (where the console is usually located for other non-FTP projects).

\n

The FTP log displays output related to the interaction with the FTP server. The screenshot below, for example, shows what happens when we create a new file called TestFile.txt. The file is created in the FTP server and when I write to it, the contents are transferred.

\n

\"Demonstrating

\n

Note:

In an FTP project, all files are stored on your FTP server; Cloud9 only stores the FTP settings. Please keep this in mind. Cloud9 IDE does not keep any copies of your files, so make sure you back them up properly. Any changes you make to these files in Cloud9 are automatically reflected on the live web server.
\n\n
" }, { "filename": "run_your_own_workspace", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Running Your Own SSH Workspace", "contents": "

Running Your Own SSH Workspace

\n

You have access to an incredibly powerful feature of Cloud9 that we like to call "running your own workspace."

\n

If you own a server that you can SSH into, you can log into that machine with Cloud9 and work on your projects remotely. To put this into perspective, you could have an entire toolchain set up on this machine--say, make with gcc, or ant with Java--edit the files with Cloud9 IDE, and build your toolchain via the IDE's terminal. Here's a video demonstrating how you could instantly compile a C program using an SSH workspace and Cloud9:

\n
\n\n
\n\n

Connection Prerequisites

\n

In order to connect Cloud9 with a server you own, you'll need two things:

\n
    \n
  1. Node.js installed on the server. This version must be between Node.js version 0.6.16 and the latest 0.8.x.
    2. \n
  2. Your public SSH key must be saved on the server at ~/.ssh/authorized_keys. This is to ensure the utmost security between your client computer and the machine you're attempting to access. Cloud9 provides you with your SSH key in the workspace dialog; it is up to you to save it to the appropriate path. For more information on SSH keys, see this article.
    3. \n
\n

Tip:

If you're behind a firewall, you can identify which IP address and port Cloud9 is running on by typing echo $OPENSHIFT_INTERNAL_IP and echo $OPENSHIFT_INTERNAL_PORT into the console. You can use this information to open any blocked connections.\n\n
\n

Creating an SSH Workspace

\n

Once you've got those requirements set up, here's how you can create an SSH workspace of your own:

\n

In the Projects tab on the Dashboard, click on the \"Project next to MY PROJECTS and choose the option to Create a new project (see "Creating a New Project" if you need to review the steps to create a new project):
\"New

\n

In the pop-up window that appears, select SSH for the project type:
\"SSH

\n

You don't need to fill out every option provided by the dialog. Let's review what they are:

\n
    \n
  • Hostname: the domain name or IP address of the machine running your SSH server.
    • \n
  • Username: your username for the SSH server.
    • \n
  • Node.js Binary Path: the locaton of your Node.js binary. If you're not sure where it is, you can always let Cloud9 guess it for you. Otherwise, on your server, type which node, to see the full path
    • \n
  • Initial path: this is an optional parameter. You can set it as an absolute (starts with /) path. Otherwise, it'll be set to a relative path, and Cloud9 assumes that you want to start from the folder your SSH server leaves you after login (usually the home or default folder).
    • \n
  • Port: this is an optional parameter. Cloud9 will automatically try to connect on port 22
    • \n
\n

Warning:

Be careful not to put an initial path that leaves you in a location where you don't have write privileges, as that could cause problems!\n\n
\n

Fill in your SSH details and click the Login Test to verify that the settings are correct. If the test succeeds, go ahead and click Create to create your SSH connection. You'll then see your project in the Dashboard under My Projects:\n\"New

\n

When your new SSH is selected, you will see three buttons: Start Editing, SSH settings, and Delete (on the far right). SSH settings gives you access to the settings you just filled in, as well as the login test. This is useful to use in case your login credentials have changed.

\n

Warning:

Make sure that you copied your SSH key correctly! Trailing spaces are significant, so make sure your text editor on your server is not modifying the key that Cloud9 is providing you with.\n\n
\n

To get started with your SSH project, click on the Start Editing button. You'll instantly be taken to the editor, and have full access to your server's resources. As you can see in the video above, this means you can do exciting things like compiling C programs.

\n\n
" }, { - "filename": "ssh_workspaces", - "mtime": 1416998221000, - "pageTitle": "SSH Workspaces", - "contents": "

SSH Workspaces

\n

To connect Cloud9 to a server via SSH, we first need to install a few dependencies on your system. \nThis is done by an open-source installer which you can find here.

\n

Usually the installation should succeed without any issues, but on some systems you will need to install a few dependencies manually. See below for common dependency issues you might run into.

\n

Installing Python 2.7 on CentOS

\n
curl -O https://www.python.org/ftp/python/2.7.6/Python-2.7.6.tar.xz\ntar xf Python-2.7.6.tar.xz\ncd Python-2.7.6\n./configure --prefix=/usr/local\nmake && make altinstall
\n

Common errors

\n

no configure: error: "curses not found"

\n

To get around this issue make sure glibc-static is installed on the machine.

\n\n
" + "filename": "setting_up_bitbucket_workspace", + "mtime": 1416491265000, + "pageTitle": "Setting Up a Bitbucket Workspace", + "contents": "

Setting Up a Bitbucket Workspace

\n

Bitbucket is a code-hosting services that offers both git and mercurial support. Projects can be listed as private or public, absolutely free. For more information on Bitbucket, visit https://bitbucket.org.

\n

We have integrated Bitbucket into the IDE to enable you to easily work on your public and private repositories. The following article explains how you can activate your Bitbucket account in Cloud9 IDE.

\n

Bitbucket Activation

\n

You can manage your add-on services from your user profile that you can find in the dashboard. When you have just signed in, click Your Account on the top of the left-side panel. Here, you can change the settings of your account. At the bottom, you'll see a list of add-on services that are integrated into Cloud9 IDE. Click activate on the Bitbucket button:

\n

\"Add-on

\n

A new window will pop-up on your screen. This window asks you to give authorization permission for the Cloud9 IDE application to interact in various ways with Bitbucket:

\n

\"Bitbucket

\n

To finalize the activation, click on Allow. Next, you're redirected to your account page, where you'll notice that your Bitbucket account is activated. You can deactivate Bitbucket by simply clicking deactivate, which may be useful when you want to link your Bitbucket account to another Cloud9 account.

\n

Now that you have activated Bitbucket, you can start to create and manage your projects!

\n

Managing Projects

\n

There are several ways to manage Bitbucket projects in Cloud9 IDE:

\n
    \n
  • By creating a new git or mercurial project and pushing it to Bitbucket
    • \n
  • By cloning a Bitbucket project from a URL
    • \n
  • By bringing in a Bitbucket project manually
    • \n
\n

Creating a New Git Project

\n

New projects are created from the dashboard. In the left-side panel, click on the \"Project to add a new project:

\n

\"New

\n

A new window will pop-up in which you can change your settings to your preferences:

\n
    \n
  • Fill in your preferred project name in the text field
    • \n
  • Choose who will have access to the project (a feature for Premium customers)
    • \n
  • Select your project type (git, mercurial, or FTP)
    • \n
  • Choose a development server (a feature for Premium customers)
    • \n
\n

\"New

\n

After you click CREATE, the project is listed in your dashboard. Select the project to see its Project Profile, where you can start editing: \"Start

\n

There are a couple of things you should do first, before you can use all of git's power. First, you'll want to add a remote to the project. From the Cloud9 IDE command line, you can execute the following commands:

\n
git remote add [remote name] [remote url]
\n

remote url is the location of the project on Bitbucket; for example 'origin git@bitbucket.org:username/repository_name.git'. You'll have to create a Bitbucket project first in order to generate this URL. Adding a remote URL lets you freely push and pull your project.

\n

Next, create a few new files inside your project. By default, you should already have a README.md. You can add these files to git with the following command:

\n
git add [file1, file2, file3, ...]
\n

Finally, create a commit that you can push to your remote:

\n
git commit -m 'added new files'
\n

Don't forget to push this commit out to Bitbucket:

\n
git push [remote name] master
\n

Ta-da! Your project is developed on Cloud9, and stored in Bitbucket.

\n

Cloning Projects from a URL

\n

You can also create a project in Cloud9 IDE by cloning it from a URL. Once again, click on the \"Project, and select Clone from URL. A new window pops up, asking you:

\n
    \n
  • to enter a Source URL
    • \n
  • to choose who will have access to the project (Premium feature)
    • \n
  • to choose a development server (Premium feature)
    • \n
\n

\"Clone

\n

You can find an examples of a Bitbucket URL on any of their repo description pages:

\n

\"Bitbucket

\n

Paste the URL in the source field and click CHECKOUT. In the left-side panel, you'll see the project and its status turn into "Cloning in Progress". When this process is completed you can open the project and start editing it, just like any other project.

\n

Clone Projects Already On Bitbucket

\n

When you provide Cloud9 IDE with your Bitbucket credentials, it provides a list of projects you haven't yet imported into the editor:

\n

\"Bitbucket

\n

From this list, clicking on a project and selecting CLONE TO EDIT brings the repo into the IDE, just as if you cloned it from a URL.

\n\n
" }, { "filename": "setting_up_github_workspace", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Setting Up a GitHub Workspace", "contents": "

Setting Up a GitHub Workspace

\n

GitHub is a code hosting service which offers you a lot of features to manage your public and private git repositories. For more information about GitHub and how to use it, visit https://github.com.

\n

We have integrated GitHub into the IDE to enable you to easily work on your public and private Git repositories. The following article explains how you can activate your GitHub account in Cloud9 IDE.

\n

GitHub Activation

\n

You can manage your add-on services from your user profile that you can find in the dashboard. When you have just signed in, click Your Account on the top of the left-side panel. Here, you can change the settings of your account. At the bottom, you'll see a list of add-on services that are integrated into Cloud9 IDE. Click activate on the GitHub button:

\n

\"Add-on

\n

A new window will pop-up on your screen. This window asks you to give authorization permission for the Cloud9 IDE application to interact in various ways with GitHub:

\n

\"GitHub

\n

To finalize the activation, click on Allow. Next, you're redirected to your account page, where you'll notice that your GitHub account is activated. You can deactivate GitHub by simply clicking deactivate, which may be useful when you want to link your GitHub account to another Cloud9 account.

\n

Now that you have activated GitHub, you can start to create and manage git projects!

\n

Managing Git Projects

\n

There are several ways to manage GitHub projects in Cloud9 IDE:

\n
    \n
  • By creating a new git project and pushing it to GitHub
    • \n
  • By cloning a GitHub project from a URL
    • \n
  • By bringing in a GitHub project manually
    • \n
\n

Creating a New Git Project

\n

New projects are created from the dashboard. In the left-side panel, click on the \"Project to add a new project:

\n

\"New

\n

A new window will pop-up in which you can change your settings to your preferences:

\n
    \n
  • Fill in your preferred project name in the text field
    • \n
  • Choose who will have access to the project (a feature for Premium customers)
    • \n
  • Select your project type (git, mercurial, or FTP)
    • \n
  • Choose a development server (a feature for Premium customers)\n{: #setupOptions}
    • \n
\n

\"New

\n

Select git as your project type. After you click CREATE, the project is listed in your dashboard. Select the project to see its Project Profile, where you can start editing: \"Start

\n

There are a couple of things you should do first, before you can use all of git's power. First, you'll want to add a remote to the project. From the Cloud9 IDE command line, you can execute the following commands:

\n
git remote add [remote name] [remote url]
\n

remote url is the location of the project on GitHub; for example 'git@github.com:/ajaxorg/node_chat'. You'll have to create a GitHub project first in order to generate this URL. Adding a remote URL lets you freely push and pull your project.

\n

Next, create a few new files inside your project. By default, you should already have a README.md. You can add these files to git with the following command:

\n
git add [file1, file2, file3, ...]
\n

Finally, create a commit that you can push to your remote:

\n
git commit -m 'added new files'
\n

Don't forget to push this commit out to GitHub:

\n
git push [remote name] master
\n

Ta-da! Your project is developed on Cloud9, and stored in GitHub.

\n

Cloning Projects from a URL

\n

You can also create a project in Cloud9 IDE by cloning it from a URL. Once again, click on the \"Project, and select Clone from URL. A new window pops up, asking you:

\n
    \n
  • to enter a Source URL
    • \n
  • to choose who will have access to the project (Premium feature)
    • \n
  • to choose a development server (Premium feature)
    {: #cloningOptions}
    • \n
\n

\"Clone

\n

You can find an examples of a GitHub URL on any of their repo description pages:

\n

\"GitHub

\n

Paste the URL in the source field and click CHECKOUT. In the left-side panel, you'll see the project and its status turn into "Cloning in Progress". When this process is completed you can open the project and start editing it, just like any other project.

\n

Clone Projects Already On GitHub

\n

When you provide Cloud9 IDE with your GitHub credentials, it provides a list of projects you haven't yet imported into the editor:

\n

\"GitHub

\n

From this list, clicking on a project and selecting CLONE TO EDIT brings the repo into the IDE, just as if you cloned it from a URL.

\n\n
" }, + { + "filename": "ssh_workspaces", + "mtime": 1416491265000, + "pageTitle": "SSH Workspaces", + "contents": "

SSH Workspaces

\n

To connect Cloud9 to a server via SSH, we first need to install a few dependencies on your system. \nThis is done by an open-source installer which you can find here.

\n

Usually the installation should succeed without any issues, but on some systems you will need to install a few dependencies manually. See below for common dependency issues you might run into.

\n

Installing Python 2.7 on CentOS

\n
curl -O https://www.python.org/ftp/python/2.7.6/Python-2.7.6.tar.xz\ntar xf Python-2.7.6.tar.xz\ncd Python-2.7.6\n./configure --prefix=/usr/local\nmake && make altinstall
\n

Common errors

\n

no configure: error: "curses not found"

\n

To get around this issue make sure glibc-static is installed on the machine.

\n\n
" + }, { "filename": "setting_up_gitlab_workspace", - "mtime": 1412172002000, + "mtime": 1416491265000, "pageTitle": "Setting Up a GitLab workspace", "contents": "\n

Setting Up a GitLab workspace

\n

GitLab is open source Git management software used by more than 25.000 \norganizations, see http://gitlab.org/.

\n

GitLab.com offers services for on-premise GitLab installations \nand free private git repositoring on GitLab Cloud \nwith unlimited repo's and collaborators.

\n

To use your on-premise GitLab installation or GitLab Cloud please see \nthe instructions for cloning from a url.

\n\n
" } ], - "toc": "\n \n ", + "toc": "\n \n ", "baseUrl": "https://docs.c9.io", "title": "Cloud9 User Documentation" } \ No newline at end of file diff --git a/out/index.html b/out/index.html index 3707c8f..5414149 100644 --- a/out/index.html +++ b/out/index.html @@ -134,7 +134,11 @@
  • Database and Persistence
  • @@ -134,8 +140,13 @@
  • Database and Persistence
  • @@ -187,7 +195,7 @@

    Writing a PHP App

    -

    With Cloud9 IDE, you can run your PHP pages, without relying on a third-party system like Apache hosting. We run PHP version 5.5.9.

    +

    With Cloud9 IDE, you can run your PHP pages, without relying on a third-party system like Apache hosting. We run PHP version 5.3.3.

    You can choose to run PHP scripts via the command line, by typing php, followed by the name of your PHP file. However, this is not a very common use case. Most likely, you'll be running your own server and hosting PHP files.

    Here's a simple demonstration. First, create a PHP file called hello_world.php, and paste this code into it:

    <html>
@@ -218,7 +226,8 @@
    - + +
    @@ -226,4 +235,4 @@

    - + \ No newline at end of file diff --git a/recentFiles.json b/recentFiles.json index 1ea929b..853bbe7 100644 --- a/recentFiles.json +++ b/recentFiles.json @@ -1 +1 @@ -[{"filename":"java_runner","mtime":1421767722000,"pageTitle":"Java Runner"},{"filename":"deploying_code","mtime":1421766901000,"pageTitle":"Deploying Your Code"},{"filename":"deploying_via_cli","mtime":1421766795000,"pageTitle":"Deploying via the Command Line"},{"filename":"frameworks_jekyll","mtime":1421763461000,"pageTitle":"Framework: Jekyll"},{"filename":"setting_up_redis","mtime":1421763157000,"pageTitle":"Redis"}] \ No newline at end of file +[{"filename":"frameworks_wordpress","mtime":1421858826000,"pageTitle":"Getting Started with Wordpress"},{"filename":"deploying_code","mtime":1421769253000,"pageTitle":"Deploying Your Code"},{"filename":"java_runner","mtime":1421769253000,"pageTitle":"Java Runner"},{"filename":"frameworks_jekyll","mtime":1421769253000,"pageTitle":"Framework: Jekyll"},{"filename":"deploying_via_cli","mtime":1421769253000,"pageTitle":"Deploying via the Command Line"}] \ No newline at end of file diff --git a/src/frameworks/frameworks_wordpress.md b/src/frameworks/frameworks_wordpress.md index f30311d..18cafae 100644 --- a/src/frameworks/frameworks_wordpress.md +++ b/src/frameworks/frameworks_wordpress.md @@ -3,26 +3,16 @@ Wordpress was made to be simple and Wordpress on Cloud9 is no different. Here are some key docs to getting started with Wordpress. ### Run & preview your WordPress site -[Running WordPress sites][run_wordpress] -[run_wordpress]: https://docs.c9.io/running_wordpress_on_cloud9.html -[Preview your site][preview] -[preview]: https://docs.c9.io/run_an_application.html#pre-view-your-application +- [Running WordPress sites](https://docs.c9.io/running_wordpress_on_cloud9.html) +- [Preview your site](https://docs.c9.io/run_an_application.html#pre-view-your-application) ### Build & access your database -[PHP documentation][phpapp] -[phpapp]: https://docs.c9.io/writing_a_php_app.html - -[Using MySQL][mysql] -[mysql]: https://docs.c9.io/setting_up_mysql.html - -[phpMyAdmin][phpMyAdmin] -[phpMyAdmin]: https://docs.c9.io/setting_up_phpmyadmin.html +- [PHP documentation](https://docs.c9.io/writing_a_php_app.html) +- [Using MySQL](https://docs.c9.io/setting_up_mysql.html) +- [phpMyAdmin](https://docs.c9.io/setting_up_phpmyadmin.html) ### Deployment -[Deploying your site][deploy] -[deploy]: https://docs.c9.io/deploying_via_cli.html - -[Mounting FTP][ftp] -[ftp]: https://c9.io/site/blog/2014/12/ftp-sftp-mounting-beta \ No newline at end of file +- [Deploying your site](https://docs.c9.io/deploying_via_cli.html) +- [Mounting FTP](https://c9.io/site/blog/2014/12/ftp-sftp-mounting-beta) \ No newline at end of file From 8e58b75a2cb52ca4f31d2398056ab9d1ee0f7c47 Mon Sep 17 00:00:00 2001 From: Brady Dowling Date: Wed, 21 Jan 2015 17:07:53 +0000 Subject: [PATCH 20/33] Updated Google Analytics code --- assets/javascripts/ga.js | 17 ++++++----------- recentFiles.json | 2 +- 2 files changed, 7 insertions(+), 12 deletions(-) diff --git a/assets/javascripts/ga.js b/assets/javascripts/ga.js index b9e9ad7..94723a8 100644 --- a/assets/javascripts/ga.js +++ b/assets/javascripts/ga.js @@ -1,11 +1,6 @@ - var _gaq = _gaq || []; - _gaq.push(['_setAccount', 'UA-18736001-1']); - _gaq.push(['_setDomainName', 'c9.io']); - _gaq.push(['_setAllowLinker', true]); - _gaq.push(['_trackPageview']); - - (function() { - var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; - ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; - var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); - })(); \ No newline at end of file + (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ + (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), + m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) + })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); + ga('create', 'UA-58752400-1', 'auto'); + ga('send', 'pageview'); \ No newline at end of file diff --git a/recentFiles.json b/recentFiles.json index 853bbe7..d20e0ab 100644 --- a/recentFiles.json +++ b/recentFiles.json @@ -1 +1 @@ -[{"filename":"frameworks_wordpress","mtime":1421858826000,"pageTitle":"Getting Started with Wordpress"},{"filename":"deploying_code","mtime":1421769253000,"pageTitle":"Deploying Your Code"},{"filename":"java_runner","mtime":1421769253000,"pageTitle":"Java Runner"},{"filename":"frameworks_jekyll","mtime":1421769253000,"pageTitle":"Framework: Jekyll"},{"filename":"deploying_via_cli","mtime":1421769253000,"pageTitle":"Deploying via the Command Line"}] \ No newline at end of file +[{"filename":"frameworks_wordpress","mtime":1421859765000,"pageTitle":"Getting Started with Wordpress"},{"filename":"deploying_code","mtime":1421769253000,"pageTitle":"Deploying Your Code"},{"filename":"java_runner","mtime":1421769253000,"pageTitle":"Java Runner"},{"filename":"frameworks_jekyll","mtime":1421769253000,"pageTitle":"Framework: Jekyll"},{"filename":"deploying_via_cli","mtime":1421769253000,"pageTitle":"Deploying via the Command Line"}] \ No newline at end of file From 3cb8fa09b2df6c665877bb1237605808d08e901e Mon Sep 17 00:00:00 2001 From: Murukesh Mohanan Date: Fri, 23 Jan 2015 22:45:04 +0530 Subject: [PATCH 21/33] Update setting_up_postgresql.md tidied up double usage of `sudo` to fix #158 --- src/persistence/setting_up_postgresql.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/persistence/setting_up_postgresql.md b/src/persistence/setting_up_postgresql.md index eec2583..a5d4fc3 100644 --- a/src/persistence/setting_up_postgresql.md +++ b/src/persistence/setting_up_postgresql.md @@ -10,7 +10,7 @@ PostgreSQL comes preinstalled on every Cloud9 workspace, yay. ### Set the "postgres" user password - $ sudo sudo -u postgres psql + $ sudo -u postgres psql psql (9.3.4, server 9.3.5) Type "help" for help. @@ -21,16 +21,16 @@ PostgreSQL comes preinstalled on every Cloud9 workspace, yay. ## Connect to the service - $ sudo sudo -u postgres psql + $ sudo -u postgres psql ## Create a PostgreSQL database Make sure you have logged into the PostgreSQL terminal and then you can just run: - $ sudo sudo -u postgres psql + $ sudo -u postgres psql postgres=# create database "groceries"; ## List all databases - $ sudo sudo -u postgres psql - postgres=# \list \ No newline at end of file + $ sudo -u postgres psql + postgres=# \list From 5174fb77778b1e86ffceeadb84ab136800600d5a Mon Sep 17 00:00:00 2001 From: Brady Dowling Date: Tue, 27 Jan 2015 04:16:07 +0000 Subject: [PATCH 22/33] Added doc with workspace details for picking a plan --- out/writing_a_php_app.html | 4 +- recentFiles.json | 2 +- src/getting_started/picking_a_plan.md | 60 +++++++++++++++++++++++++++ templates/default/toc.jade | 2 + 4 files changed, 66 insertions(+), 2 deletions(-) create mode 100644 src/getting_started/picking_a_plan.md diff --git a/out/writing_a_php_app.html b/out/writing_a_php_app.html index 29568df..0c595b5 100644 --- a/out/writing_a_php_app.html +++ b/out/writing_a_php_app.html @@ -34,7 +34,9 @@
  • Getting Started
      -
    • Create a workspace
      • +
    • Create a workspace +
    • Picking a Plan +
    • Run an application
    • Set up a database
    • Share a workspace
      • diff --git a/recentFiles.json b/recentFiles.json index d20e0ab..9611e6a 100644 --- a/recentFiles.json +++ b/recentFiles.json @@ -1 +1 @@ -[{"filename":"frameworks_wordpress","mtime":1421859765000,"pageTitle":"Getting Started with Wordpress"},{"filename":"deploying_code","mtime":1421769253000,"pageTitle":"Deploying Your Code"},{"filename":"java_runner","mtime":1421769253000,"pageTitle":"Java Runner"},{"filename":"frameworks_jekyll","mtime":1421769253000,"pageTitle":"Framework: Jekyll"},{"filename":"deploying_via_cli","mtime":1421769253000,"pageTitle":"Deploying via the Command Line"}] \ No newline at end of file +[{"filename":"picking_a_plan","mtime":1422331417000,"pageTitle":"Picking a Plan"},{"filename":"frameworks_wordpress","mtime":1421859765000,"pageTitle":"Getting Started with Wordpress"},{"filename":"deploying_code","mtime":1421769253000,"pageTitle":"Deploying Your Code"},{"filename":"java_runner","mtime":1421769253000,"pageTitle":"Java Runner"},{"filename":"frameworks_jekyll","mtime":1421769253000,"pageTitle":"Framework: Jekyll"}] \ No newline at end of file diff --git a/src/getting_started/picking_a_plan.md b/src/getting_started/picking_a_plan.md new file mode 100644 index 0000000..883b605 --- /dev/null +++ b/src/getting_started/picking_a_plan.md @@ -0,0 +1,60 @@ +# Picking a Plan + +The [Plans and Pricing Page](https://c9.io/web/site/pricing) has the basics for the available plans but here, we'll break down the details of workspaces. + +## Workspace Choices +With Cloud9, you write code, run commands, and build applications in workspaces (virtual machines) hosted on Google Cloud. You're free to resize workspaces at any time so don't fret about their initial sizing. Following are the different types of workspaces and their properties: + +### Micro Workspace +- 512MB RAM +- 1GB Disk space +- 1 CPU +- Private + +### Small Workspace +- 512MB RAM +- 5GB Disk space +- 1 CPU +- Private + +### Medium Workspace +- 1GB RAM +- 10GB Disk space +- 1 CPU +- Private + +### Large Workspace +- 2GB RAM +- 20GB Disk space +- 1 CPU +- Private + +### SSH Workspace +- Resources determined by user +- Private + +### Community Workspaces +- 512MB RAM +- 1GB Disk space +- 1 CPU +- Publicly readable +- Archived after a week of inactivity (restored unchanged when you open it again) + +Given the resources from your plan, you may make as many private workspaces as you'd like. For example, if you're signed up for the large plan with 80gb of storage, you could use that to have 4 different large workspaces, each with 20gb of storage. With those 4 workspaces, you would have no resources left to make further private workspaces although you could still make more community workspaces. + +## Reaching the Limits + +When a workspace reaches its RAM limit, you will be notified and processes may be killed to stay within the limit. + +When the storage limit within a workspace is reached, the terminal will display a message to let you know. Any downloads will be stopped. + +## All plans + +The following features are provided with the free plan and all paid plans. + +- __Unlimited Community Workspaces__ - Each community workspace is readable by anyone, like a public GitHub repository. +- __Team collaboration__ - You can invite coworkers, classmates, and anyone with an email address or Cloud9 account to work with you, real-time, giving read/write privileges to whomever you choose. Collaboration takes place live so you can see one another manipulating code real-time. +- __VMs hosted on Google Cloud__ - Each VM/workspace is allotted resources according to your chosing. Those resources are important because each workspace is running on a VM hosted on Google Cloud. +- __Sudo Shell Access/Terminal__ - Sudo access allows you to install your own programs or languages, giving them nearly the same amount of access they might have on a local machine. +- __SSD Performance__ - VM's are hosted on SSD's to speed up processes and development. +- __Running on Docker__ - Workspaces are powered by Docker Ubuntu containers that give you full freedom over your environment, including sudo rights. \ No newline at end of file diff --git a/templates/default/toc.jade b/templates/default/toc.jade index eafebd1..76a2ae2 100644 --- a/templates/default/toc.jade +++ b/templates/default/toc.jade @@ -20,6 +20,8 @@ ul li.nav-submenu-item a(href='create_a_workspace.html') Create a workspace + li.nav-submenu-item + a(href='picking_a_plan.html') Picking a Plan li.nav-submenu-item a(href='run_an_application.html') Run an application li.nav-submenu-item From c9bca5d8cb9d79a3b392c1705bd759706d62831c Mon Sep 17 00:00:00 2001 From: Brady Dowling Date: Tue, 27 Jan 2015 21:00:17 +0000 Subject: [PATCH 23/33] Double sudo is needed so it was re-added --- src/persistence/setting_up_postgresql.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/src/persistence/setting_up_postgresql.md b/src/persistence/setting_up_postgresql.md index a5d4fc3..1ffe936 100644 --- a/src/persistence/setting_up_postgresql.md +++ b/src/persistence/setting_up_postgresql.md @@ -10,27 +10,27 @@ PostgreSQL comes preinstalled on every Cloud9 workspace, yay. ### Set the "postgres" user password - $ sudo -u postgres psql + $ sudo sudo -u postgres psql psql (9.3.4, server 9.3.5) Type "help" for help. - + postgres=# \password - Enter new password: - Enter it again: + Enter new password: + Enter it again: postgres=# \q ## Connect to the service - $ sudo -u postgres psql + $ sudo sudo -u postgres psql ## Create a PostgreSQL database Make sure you have logged into the PostgreSQL terminal and then you can just run: - $ sudo -u postgres psql + $ sudo sudo -u postgres psql postgres=# create database "groceries"; - + ## List all databases - $ sudo -u postgres psql + $ sudo sudo -u postgres psql postgres=# \list From fc465cba97da3001ae4cb975ac1b56d6164c2b47 Mon Sep 17 00:00:00 2001 From: Brady Dowling Date: Tue, 27 Jan 2015 21:06:43 +0000 Subject: [PATCH 24/33] Added FAQ about SSHing into workspace --- recentFiles.json | 2 +- src/faq/faq_general.md | 20 ++++++++++++-------- 2 files changed, 13 insertions(+), 9 deletions(-) diff --git a/recentFiles.json b/recentFiles.json index d20e0ab..ac935a5 100644 --- a/recentFiles.json +++ b/recentFiles.json @@ -1 +1 @@ -[{"filename":"frameworks_wordpress","mtime":1421859765000,"pageTitle":"Getting Started with Wordpress"},{"filename":"deploying_code","mtime":1421769253000,"pageTitle":"Deploying Your Code"},{"filename":"java_runner","mtime":1421769253000,"pageTitle":"Java Runner"},{"filename":"frameworks_jekyll","mtime":1421769253000,"pageTitle":"Framework: Jekyll"},{"filename":"deploying_via_cli","mtime":1421769253000,"pageTitle":"Deploying via the Command Line"}] \ No newline at end of file +[{"filename":"setting_up_postgresql","mtime":1422392332000,"pageTitle":"PostgreSQL"},{"filename":"frameworks_wordpress","mtime":1421859765000,"pageTitle":"Getting Started with Wordpress"},{"filename":"deploying_code","mtime":1421769253000,"pageTitle":"Deploying Your Code"},{"filename":"java_runner","mtime":1421769253000,"pageTitle":"Java Runner"},{"filename":"frameworks_jekyll","mtime":1421769253000,"pageTitle":"Framework: Jekyll"}] \ No newline at end of file diff --git a/src/faq/faq_general.md b/src/faq/faq_general.md index 2511b32..864e59e 100644 --- a/src/faq/faq_general.md +++ b/src/faq/faq_general.md @@ -1,19 +1,19 @@ # FAQ: General ### Can I use FTP workspaces on Cloud9? -Yes, Cloud9 supports FTP workspaces that allow you to edit your files directly on your FTP server. +Yes, Cloud9 supports FTP workspaces that allow you to edit your files directly on your FTP server. Currently FTP workspaces still open in the old version of Cloud9, but soon we'll also support FTP workspaces with the new version of Cloud9. One thing that was removed for reliability reasons in the new version of Cloud9, is the ability to deploy over FTP from a regular workspace. We're bringing back those features in a new format and with much higher reliability in the coming months. -### How do I deploy to Heroku/Openshift/Azure/...? +### How do I deploy to Heroku/Openshift/Azure/...? See [Deploying via CLI](./deploying_via_cli.html). -### Can I connect to SMTP servers (port 25)? +### Can I connect to SMTP servers (port 25)? No, this is not supported by our hosting platform. It does currently allow access to the GMail servers though, so you can use that service during development. -### My workspace says it's out of quota. how do I fix it? +### My workspace says it's out of quota. how do I fix it? You can inspect your current quota usage with the df command in the Terminal: $ df @@ -30,10 +30,10 @@ Alternatively, try `du-c9` for seeing all files you added to your workspace and You can sign into Cloud9 with your github or bitbucket account and set that up to use two-factor authentication. We don't currently provide an option to directly setup your Cloud9 account for two-factor authentication. -### I can't preview my running app. +### I can't preview my running app. Try using port 8080 instead, which often solves this case. -### EADDRINUSE: My app complains that the address/port is in use +### EADDRINUSE: My app complains that the address/port is in use Applications won't start if another application is already listening to the same port. In order to fix it you first need to find out which process that is: $ netstat -nlp | grep $PORT @@ -59,8 +59,8 @@ ensures maximum portability. To open these files, you can use something like ## How can I share a single directory of a private workspace -Sometime you might want others to open a file or directory in the browser -without opening up the whole workspace. This can be done by starting a small +Sometime you might want others to open a file or directory in the browser +without opening up the whole workspace. This can be done by starting a small http server in that directory and make sure that the running application is public. To make the running application public you have to click the "sharing" button at @@ -70,3 +70,7 @@ To run the server open a terminal and do $ cd /dir/i/want/to/share $ python3 -m http.server 8080 + +## How do I SSH into my workspace? + +At the moment, users cannot SSH into their Cloud9 workspaces. You may setup an SSH workspace which will access the files on another SSH server but you cannot SSH into your workspace from another machine. From 78fee71814a4be9f4a71926114459b18c753423c Mon Sep 17 00:00:00 2001 From: Brady Dowling Date: Wed, 28 Jan 2015 14:19:33 +0000 Subject: [PATCH 25/33] Changed section for picking a plan, fixed formatting --- out/writing_a_php_app.html | 5 +-- recentFiles.json | 2 +- src/getting_started/picking_a_plan.md | 60 --------------------------- templates/default/toc.jade | 4 +- 4 files changed, 5 insertions(+), 66 deletions(-) delete mode 100644 src/getting_started/picking_a_plan.md diff --git a/out/writing_a_php_app.html b/out/writing_a_php_app.html index 0c595b5..b4b4cfe 100644 --- a/out/writing_a_php_app.html +++ b/out/writing_a_php_app.html @@ -34,9 +34,7 @@
    • Getting Started
    • diff --git a/recentFiles.json b/recentFiles.json index 83953b8..66fc59c 100644 --- a/recentFiles.json +++ b/recentFiles.json @@ -1 +1 @@ -[{"filename":"setting_up_postgresql","mtime":1422392332000,"pageTitle":"PostgreSQL"},{"filename":"frameworks_wordpress","mtime":1421859765000,"pageTitle":"Getting Started with Wordpress"},{"filename":"deploying_code","mtime":1421769253000,"pageTitle":"Deploying Your Code"},{"filename":"java_runner","mtime":1421769253000,"pageTitle":"Java Runner"},{"filename":"frameworks_jekyll","mtime":1421769253000,"pageTitle":"Framework: Jekyll"}] +[{"filename":"faq_general","mtime":1422453385000,"pageTitle":"FAQ: General"},{"filename":"setting_up_postgresql","mtime":1422453385000,"pageTitle":"PostgreSQL"},{"filename":"picking_a_plan","mtime":1422453317000,"pageTitle":"Picking a Plan"},{"filename":"frameworks_wordpress","mtime":1421859765000,"pageTitle":"Getting Started with Wordpress"},{"filename":"deploying_code","mtime":1421769253000,"pageTitle":"Deploying Your Code"}] \ No newline at end of file diff --git a/src/getting_started/picking_a_plan.md b/src/getting_started/picking_a_plan.md deleted file mode 100644 index 883b605..0000000 --- a/src/getting_started/picking_a_plan.md +++ /dev/null @@ -1,60 +0,0 @@ -# Picking a Plan - -The [Plans and Pricing Page](https://c9.io/web/site/pricing) has the basics for the available plans but here, we'll break down the details of workspaces. - -## Workspace Choices -With Cloud9, you write code, run commands, and build applications in workspaces (virtual machines) hosted on Google Cloud. You're free to resize workspaces at any time so don't fret about their initial sizing. Following are the different types of workspaces and their properties: - -### Micro Workspace -- 512MB RAM -- 1GB Disk space -- 1 CPU -- Private - -### Small Workspace -- 512MB RAM -- 5GB Disk space -- 1 CPU -- Private - -### Medium Workspace -- 1GB RAM -- 10GB Disk space -- 1 CPU -- Private - -### Large Workspace -- 2GB RAM -- 20GB Disk space -- 1 CPU -- Private - -### SSH Workspace -- Resources determined by user -- Private - -### Community Workspaces -- 512MB RAM -- 1GB Disk space -- 1 CPU -- Publicly readable -- Archived after a week of inactivity (restored unchanged when you open it again) - -Given the resources from your plan, you may make as many private workspaces as you'd like. For example, if you're signed up for the large plan with 80gb of storage, you could use that to have 4 different large workspaces, each with 20gb of storage. With those 4 workspaces, you would have no resources left to make further private workspaces although you could still make more community workspaces. - -## Reaching the Limits - -When a workspace reaches its RAM limit, you will be notified and processes may be killed to stay within the limit. - -When the storage limit within a workspace is reached, the terminal will display a message to let you know. Any downloads will be stopped. - -## All plans - -The following features are provided with the free plan and all paid plans. - -- __Unlimited Community Workspaces__ - Each community workspace is readable by anyone, like a public GitHub repository. -- __Team collaboration__ - You can invite coworkers, classmates, and anyone with an email address or Cloud9 account to work with you, real-time, giving read/write privileges to whomever you choose. Collaboration takes place live so you can see one another manipulating code real-time. -- __VMs hosted on Google Cloud__ - Each VM/workspace is allotted resources according to your chosing. Those resources are important because each workspace is running on a VM hosted on Google Cloud. -- __Sudo Shell Access/Terminal__ - Sudo access allows you to install your own programs or languages, giving them nearly the same amount of access they might have on a local machine. -- __SSD Performance__ - VM's are hosted on SSD's to speed up processes and development. -- __Running on Docker__ - Workspaces are powered by Docker Ubuntu containers that give you full freedom over your environment, including sudo rights. \ No newline at end of file diff --git a/templates/default/toc.jade b/templates/default/toc.jade index 76a2ae2..3a5b702 100644 --- a/templates/default/toc.jade +++ b/templates/default/toc.jade @@ -20,8 +20,6 @@ ul li.nav-submenu-item a(href='create_a_workspace.html') Create a workspace - li.nav-submenu-item - a(href='picking_a_plan.html') Picking a Plan li.nav-submenu-item a(href='run_an_application.html') Run an application li.nav-submenu-item @@ -111,6 +109,8 @@ a(href='ftp_workspaces.html') Creating an FTP Workspace li.nav-submenu-item a(href='run_your_own_workspace.html') Running Your Own SSH Workspace + li.nav-submenu-item + a(href='picking_a_plan.html') Picking a Plan li.nav-section .nav-section-header a(href='javascript:void(0)') Running and Debugging Code From 6897ca72a18b5d31b44eceaedaeb3f28c27c3423 Mon Sep 17 00:00:00 2001 From: Brady Dowling Date: Wed, 28 Jan 2015 14:20:09 +0000 Subject: [PATCH 26/33] Changed section for picking a plan, fixed formatting --- src/workspaces/picking_a_plan.md | 60 ++++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+) create mode 100644 src/workspaces/picking_a_plan.md diff --git a/src/workspaces/picking_a_plan.md b/src/workspaces/picking_a_plan.md new file mode 100644 index 0000000..883b605 --- /dev/null +++ b/src/workspaces/picking_a_plan.md @@ -0,0 +1,60 @@ +# Picking a Plan + +The [Plans and Pricing Page](https://c9.io/web/site/pricing) has the basics for the available plans but here, we'll break down the details of workspaces. + +## Workspace Choices +With Cloud9, you write code, run commands, and build applications in workspaces (virtual machines) hosted on Google Cloud. You're free to resize workspaces at any time so don't fret about their initial sizing. Following are the different types of workspaces and their properties: + +### Micro Workspace +- 512MB RAM +- 1GB Disk space +- 1 CPU +- Private + +### Small Workspace +- 512MB RAM +- 5GB Disk space +- 1 CPU +- Private + +### Medium Workspace +- 1GB RAM +- 10GB Disk space +- 1 CPU +- Private + +### Large Workspace +- 2GB RAM +- 20GB Disk space +- 1 CPU +- Private + +### SSH Workspace +- Resources determined by user +- Private + +### Community Workspaces +- 512MB RAM +- 1GB Disk space +- 1 CPU +- Publicly readable +- Archived after a week of inactivity (restored unchanged when you open it again) + +Given the resources from your plan, you may make as many private workspaces as you'd like. For example, if you're signed up for the large plan with 80gb of storage, you could use that to have 4 different large workspaces, each with 20gb of storage. With those 4 workspaces, you would have no resources left to make further private workspaces although you could still make more community workspaces. + +## Reaching the Limits + +When a workspace reaches its RAM limit, you will be notified and processes may be killed to stay within the limit. + +When the storage limit within a workspace is reached, the terminal will display a message to let you know. Any downloads will be stopped. + +## All plans + +The following features are provided with the free plan and all paid plans. + +- __Unlimited Community Workspaces__ - Each community workspace is readable by anyone, like a public GitHub repository. +- __Team collaboration__ - You can invite coworkers, classmates, and anyone with an email address or Cloud9 account to work with you, real-time, giving read/write privileges to whomever you choose. Collaboration takes place live so you can see one another manipulating code real-time. +- __VMs hosted on Google Cloud__ - Each VM/workspace is allotted resources according to your chosing. Those resources are important because each workspace is running on a VM hosted on Google Cloud. +- __Sudo Shell Access/Terminal__ - Sudo access allows you to install your own programs or languages, giving them nearly the same amount of access they might have on a local machine. +- __SSD Performance__ - VM's are hosted on SSD's to speed up processes and development. +- __Running on Docker__ - Workspaces are powered by Docker Ubuntu containers that give you full freedom over your environment, including sudo rights. \ No newline at end of file From 2587b7533c306336d33632997b208a430ef27dcf Mon Sep 17 00:00:00 2001 From: Mutahhir Date: Mon, 2 Feb 2015 12:47:29 +0500 Subject: [PATCH 27/33] Add Python CGI tutorial draft --- resources/images/apacheRunConfiguration.png | Bin 0 -> 39115 bytes resources/images/newRunConfiguration-new.png | Bin 0 -> 31191 bytes resources/images/saveRunConfiguration.png | Bin 0 -> 26285 bytes .../running_python_cgi.md | 115 ++++++++++++++++++ 4 files changed, 115 insertions(+) create mode 100644 resources/images/apacheRunConfiguration.png create mode 100644 resources/images/newRunConfiguration-new.png create mode 100644 resources/images/saveRunConfiguration.png create mode 100644 src/running_and_debugging/running_python_cgi.md diff --git a/resources/images/apacheRunConfiguration.png b/resources/images/apacheRunConfiguration.png new file mode 100644 index 0000000000000000000000000000000000000000..cd2ac28893cf8ceedc075fa6a76cf55aa8b06ffa GIT binary patch literal 39115 zcmdS9Wl&vPyETX_W%hVG`PFFyL*rT!686GaCevB?(Xicy>{N)_kLAf z)m_!q-Bo>l1s-`G zt8RUKbv&)1@{dz1DilG8P~$8J=P@|FPOfP3yf+-eP^@cEQtf@nOC*Ekb#>6MtT#wb^UO{!qd<h3g$fEh;}&?&{7xs-4jKyCQ%1oJ87k2Q zsvZTVD@6oKs-(klD>tvMTP@{ zEE8onVSY9;?y%CEHh!MhFXEC^FOTOwrhe~;HaFmIS?xCAliS~o`BN*vEC`b@>siC3 zfDwZNq0rHa;n0x-))d{oAaw9y`Y;((GPsy}xtXcMWI&s;rr2O(6@ewy6qQ1DpIRAT zhz|IU%ko63A76=(1fcvL-g^1mz4G9|=_1Xp^T&UG;h|=GlXbZW<#hR$x|ik|U+nos z1QtdwxQv?w3=;Q$*KCNL4ejKQ!3?YEM{M_&q#YM7fEgX-R1iNupaqPy6_B?ENBeer z?L$4(fiSEY^zjL&5B3V>s|Xl_5)NJzip*a@ z+>8tlWEsTP36BvGCYBFo#gIgo2>aAcCC;|NxdFX_Zvev*sV)pdi6Je9NUx*Zx=aY9TFoYuCvgPfl#nEpt zBS6?NhtuzLBNIHA{!*Q{-DH(d@t3=S!7I z1{1~${6*NJ*dlP?y63p3K}wSF?}?xaqssUh^fT2sZX1a{QzbpA<6tnY^K1V?|3k_( z)*Jcw>=cERMD|Yz+q}jpmF*vmznD}RMw;+-yTl)pEF$wIYX>Yx34{qGJb&=ydVGg1 zjr}uC0ruBpk;;_L0Xuw%*tf0-iU5l5c`s zz^@psOg6VPXWen%Io-qDJKPc6>0D6U8Q&4#yPjul`}Vhi!L)j0==64A(jcmVZjs6&q$29WjKZ{V z+^IgHPh+BB2rw>C@zPLJn$RcHsnXvl5iylgkx=_6J;mI83(61r(G4Ar6OJ!!BTfJJ z-QTZ&S>9JB<|wBt|D5__9#x&}l<$;!g@qp!)hLr96Fy|95%ed-s@^K~$dBl&oF?PP zQY9PpOv=$X`EO-OS<2b(=V*;+t7*Ly-+j4K9#U)0yZbDy{r=OhPv*+0+U}7KAr3z- zxUlh)gp)9n3V$1^I8HlFt4_OfXw>M{Oj=MJC_8Ij!yafK91^4voD*CVkh1r%KXZKM z2(96+KB_@AU!MMGNoZMUS!c;~XtqbW$G+z^oirOg)l$TlNAnB!kJ?YJpG>)ECo$-Y$^tGCo!$fty67ztf=&`%~T9I>LeToPZ$JdC@pCY z4Gy_DSvk)+t!qJx47Gh$eYFv`(en!i@JD}+V&+>azgNdrwXOTvm%Gy1yX_Vor5w2R zg&%C~I*pr;&(HCUx=%?AP>uf_Oq!lvtm$?BJ3Lj=Zr!Op?p^l?i>4E67pp4&r?7a} zee?|zTN#$l%KSrMJu7(&hGb^hL{l-$CD%<(1@P)4lGMuHga;eJT>PD)dii zM}KO68d%f7sDK!FZ_o@HBgls|msAOz73(*t$A>Gi6n%C5xk9^yvyHQR&|ug_*iWgZ z{)7H#+Pb2_@p`k@y+f8GmUtF{MYy`-IZkwX!XMat7=>7_&nQwCla5&ke+s4@`B}U|TdM&?L&+Q_V6pgvsHQ&k*jNl<~ymD{V ze+h=E4M+_5Wmwyn7CRZcOY~~rdD`6~TGM%v5R?#3Lla>Y@l`%NgV)2Ng!|8(M!5ao zZKaoqqlurD*_9oW9}5o$-wZeos*MC?;r}WxGAm6i`oJH_^TX*zJIQi7!}05`#mHsm zs6d+z@fQL6j&o7@XcO6CiI+(Cny`iL1+?$YOai~yN-RshmzCAaG^KmK(UNYyIRE`R zy^At~q8gGsE(}U~c>Hboa zkM5z*AZ#@JFxoUJr+||0)KuB{>XZ7V{UO#djWw(XEOB5+U|pz8=tJgL0q--b!z%w> z#!<crZMF>#C&c9Tu z{T5DppGS$*G1^mgA&saS@f6|ssbxTdj^%f+#gc{Y)FZo`CAB4w#o*zZ^UC4Pp343y z7l@^r^_yWiOLA17?1M~MN>U1GwNxc?t;4*5eu-h89(`q!iDY%?5iYSHpBzt%9f@7T z;ljSl^7HRLiP0(@;}sh33vaZ0fekB|H|>n(?MTl zFrCKeg=%<4f>4=aiEl@B??bLw$s^TjfAcC4wnF$Ax^@kRhoL@ihZ3fK_wFpl_ zq?*Qu{bB;^2>1#c-5Rw$*syN7; z3tv44R8auWWDORSXT3`MSHu&I^_N@AH>MO&Karo7)-9n&3S-k(UkRjf2yT_KlNHW4Kv{8PYv zIm~o`M^Kt5L*9EcglfSBeB$sCVcfj3+|wMI@j*P!DCAze&0y(vqTcjSp0hVQe92Ks z-K^z0bCgzswK$8R-htYE_M207H}z6WB3js`Sht9EQHAR&=Qnp|UW_j=t!S^we&8{L zw{WDQbU7(@8O)-0(p%&fnA+je-J%9;_9^w^8`S3U{8I1pl_q2-xbfp8`U|$u9XK13 zm*g`|*Y(DY&W)rEe;Mr?-?tBR{_Z^JZH&A|2J-fYVA1hxH^m#J-|u5-h34Gm@vL&J zBzyG0`cQbS+``a$|7Ea{b3n;RV}W-TC*9=2~(v!y028)fnZOY8;)}2RtTqvO955 z`zWGN4uvSOsP10CRmm0mgYiQ>v&5Vfw_LrFn-m;FE*U1B!>29({>GwQ+AmirW?6gk zEE+7j6dkssX;B$pX=K}xGj{;KT%N3S%lbnN$; ztfDH5dWF_`Fs901)qOvu?-Oa21rE&)85dCzMG;w_Dh3=?T&7EY^ZfR>|W4BSO z(WX(Nk?G3qy7_wGs`q;T0s2AZ;S@O^g&gGoWd~&%IRRx6c{UpF<74y*OFuIFN3zYI z6>;`)_R;5RSR4uOQU;j|I1AnsFb(aQkeOVYAnkbUr0$@7D8kXfQNhXjFwNkqd81MB z)m>fXtM@`~E0y=4fF-J>?jgb9Dd$_xdCpO*{aVFZ2F-ZQR6A=uradLl z(J~r1NHLT*oUpZj=-z|0zP+JxT(e<)=-vC+6x%TRK5Mk~V{4zc>C@Fy%tOod?2XXT zYsjy^L&kD&W^h|?W#BB}cHYXpHGfNtnua)oDoF5zx>I3DMkW|{s_L+%Vf#uH2P#Ok8zrhS8b&xyVpvtyoCQ=ikBmKyx}sJN(1Z}P{RBf?Sk z{tts%i>EDZ0+B-W9Ea1;&#;APRzyZ5M*}#6BLgpSh8bV7KL1_L-Cf1!CH z_;coW-ox%ghlAD`zUexhownxPi$(fmHH)%Jt>`A+sqArusq%@vX}8O?wVGb2@Cg}MZ--c+iw@6`w0b(VUDGbpSh@PPFi`U$R^`g z&aaZMN|x*1^7im1@SU#WG!wfv)kQYZ|1Pfjk;nI^sU>s*Ys#_Z`_kZ%^$Eqz{k3*e zVB4l=;W^_;>F9EZ=bWeDEy0Q5>En{Eo1f>}W%fDQNzQ4PW$an(lU^pp&109iqz4fc z8}VQQIORYcJ^9!+e)*p{mHVF3V9M)@OxdNPviKNuZMr zlWpQTU{_)&^5pvxQ=YC%v_tgA=oON@Xo;w04+(GVo8QkI+sk@nKQudh`jMq|fHKqfdjE5BFmg-)<(;A6@=7W$*h3mB&ND6m*_l zuif9fts|Brg`>CL6uyoxsu$K5O{g$Dq>eXiFIN~U`_?rYj>a%&_H z#~L3z?mYHAUYX85->bEk1?XzG?QjKgT5-8pE88MJs|eXVycWFL{$Ks`>i)V)lKcCj z@GZCp*6*dE;#?aF%8C%`@SKpa*qD&;Pz4IC3pIv+yZfVkRi6S4>LjNyGI(3;Z*l(X zgTRUqRNfn~v?tx?YCvzyFjrQ0QkRwCHMF&6)HkvmeSKq+a*-3z$95T><|M#DH8oQbQ&qy|o|FtY&flQD$Oe~Dd zO#j_C@F_p!ue=K8ZpK#X;^x-IHjcm;f^3}Z{QuhjAKv`Wi2uu%8vpYpCo|9g`sM%f z=D)t=XM!x?e_7CfcI)3?f$b7R*Vtz5d?xJi=%__m95DhK!7F#!vzVuV4&-p;`-Jw!Ug%EOW{LfxC|)#%0@?r z5d}Aa!pf^6+rHw$hzf)9qx?X8#zo2s|N78|6Q7&!(JeuObfWZ8I4FZvnT{6HML#19 z`O(ov*-Wq>(8+rWaHkwT9rim&7e=^1?=I(Rhrn-;eFY~bI>(;Vzgb&=o)~Hj=#mg&$WN6Ol<>*Wwc%bazPE|jIf{&m&zYmj zlPk$pGYwm)XaPG20>>Ts@*o671WVqmF{%9DonT}NFh=neEqx$?obEOu<7i^oHrE)l1mL+PAjR73{D*D}KtdLbG zu}gVxG@<71NJiDi1;p^gi{T3+?N2PkI6#|Nj5)Ks=s#a;EMlrXuMd)H=&|)pQ9L+4 z0K=D(m2W3&F1$RRo;GHnn92oZSgzt-s{s@KL*`eAVs1JJ*p8^q@xOzg5C=||T959Z z`Ss%fM`%S>=JN00&B?Qkz0IL!uIJeii;IBMcMok3EHt|Pwxv(gAw($epWq}J3apFP z4zP(gFK@=S0c%unfnzm$Y9-d1+jktds3sE?s@00I^NK9SO>)#kM` z^Sr+Ovh(B4o98Fil)1$>vk$k!ON`Hd+2A%>zq-3P^Z4+f6TZ5+xuSoJd@zysQs1gs z#}W+1Fxm|=-gp;Z0 zDKH6)$@7XoHeRdUSl!6S6#a}1mnAK36iS_zqm}) z<~_#f$N`s?)j!T_2)4R4dzV6iFJ+I@e|B(8e!N+E#v#OYACrH3+}hS}HJbgpOQbNB z#Uau_*Kt1WA4+UX3^SV66jc z2}a(ur_;y|XUDqs>zEhYi%Q-!Pav35@SD8cxNi-CwZ<#Mg1lXe-*z`@Fnf@CYl_cB z!^l5%21eR6ku{b1Fh6ebRqb34gYegSw3qV3l!Z|F1whFP?dH(y>-!=p^f2-_%Vm-L zYqkEfi29R^2{7VfKVCs$JC$NXC+R1iN>?$VF{V;`JG(M`RTPUePmeN4U_o;jr3+sh!|K#?+5%Y2Jf#5cMOuLOJh49 za~yW-J}yLNG!Pc7X(@$IWsX*JMeJY9Z}4nUEV*cUaIHV_-Cl8`dQJ{chd$AlZ8ii8 zpQ(J4z<>_3{!ZY3i~W=*${wfP(uNyPWE6ESXeD5e%KbYmij2Ge@LWT}ND2hgxt-=e99-T@uj`m+Pl~;#R!pHk{3$$&B@ug!vlfRbEkJfh+_OA$YT4>4r&D?VaiF z+_5!mC(?nNkqO23MxP8dQDK^gCa(1tu*{5CFZh$r3RvkOA%aCChz9qd za5?bp3*V6V4SyKkpbV@NXaSchy{f-FNQSWT+Zcr{bFH+7|3fFMD#YnmbS(> zvgmKgs@J3A-m+{_^S#5swjbHKhP9;wX`Z#mmLnJiV)U9dIAUms#jU=n`|D=j&8d0x zuG=l}!4<8UOO-LvC`bz|lpHDhKyF3>3NAPBhj)0dF@`H2f)ZHUJli0F9^31fugkA2 z;Q0y;d6rf5N_D%Miw!(Pj;UMW2-9a`{Ce$II8xbK-mv)Ur;f0w5PLh-WsGSZ7@x(? zJwhzjOoiB{5E9zJFZ@iK((NXk*58>RlDqlyc+PM|C%=lZDKit#f$|iTYEQ4Lb9_6Sd{A*bT(5V=OF2sx=&W$ zsbcjz<&;Oh?`HV)5U#Xx)tWQK`}2*$s>^=)){|hIOOFud zVbOD1gzIQcZv&Okdozb3flz($0?of|>em;VE0y6kqz|Lm!M-jJS+7rhZ-@TqW**QT zX}zMKboq^iyH-vZOf(A>hn8!+59o`Y?J0vIv*|~nKtJzFF4c@haL z_|Qw)b?`1K<*w21Zq!C=%YXIELow?GD~P32hgFBWSXl6}HLN-UfW^4EBvS=u&O>A7 zJ+UgiH0AZ%DY=3@uTn*<3!m%cRAJ8BFAAW(yxQ?D^D4I*!MP=0w!J=&rm-XV>DZ>e z+d^sesnimOI!#l-?*6`slDo6b(26YdR=N))kjRmFxOi?fY?@4HpapC1c93`C(DCT+fwckTwgqNi_}# z6=rMJt-T${_PSUFnMJp=)sl z6$nfm5Uu@o*m8LM$p#ENEkuBBErEa7jkFAMUuMf2Q|v!IWa@*-e|q~-jRp?Dh+zc4 zCq>a=4-}9mT4;cXAhes+{i75XK!VKUBtM9SJY~bdU5!=1>0utD?oLWMX*~kX(P5Ip z{rHat#MPYt@f|vJ;PW>DzkdJk??6qg<0XEL_wG-(tG=f?ZLcIx1_kdP_Y1RN-lXms z5#DWo*Cn6MQd*nTCqp-fm^w-3>&tDMOFvoY97`Y3rp^|V+i}h8C(3r?!Q^>GNn&H6 zS0YMOX+3oJLb;5i4A&KDJN9R7!@iiBNT$}g7XYAR%KJQD&sz7#kx`M%LIdnUNfJQP zysG#N_kU@!=G=EPOieSKlV#J`{}#w)SirtTE^qaIT<|bT`tw_MNE-tYX-{K0Ac$8xr`R<9!f#p9|6S9dP){g?F6;g0*u-9=zG zY~YFP{G5;G##>(=EO%2!(>Mlwp3WsTtIguIeV?y6J+92u-sZlp1)?occJRasz0}jo zH@rMQE}pG-MNV(?oy}ffuw2d0PXEzhbEOeZjpkaJ^SD0P9x05H0VY=okWEHDmn0Wz z`@Q)p(?w~TjCUYRxcA4RF5?ooJmjdy4nKnAZ{|%&7Y!mAj$Yp&q?~uh@?S_1a@nMF zn2ohJI_+XpNBfgVSu?vdiM|GWH+s zCeGHy2MAFj0GScH5a=2Irq!`bqEktCO|$r6IrFFD`DT%6?DJDG@PFG{8|}Dz!E%e~ z-}BRIy2qlJ=scN?bUrk;%7++abUVyZn*oHWzVC|qUpxYlZZ0w8?bqU64hn&;w<=?mZ8TA(&jY7$u-SxBhYq%7CGekk#d6!#J(Nd*`G7I47xQTS|8p#cdr^0of3 z@LwkjWW6zNPY$0|2FP!+#fucE-vxBJ-Gq6ZWF5vL6Dje zpi3m8LA%dwca=?y*i040FMHoEyWDSoZwmEh7dP_{^}NP%`wj6zO$``-%tDiC$ygEr zgJ;8V@VON!=ejU=CdzmS3MMKcy@Z=Se;j3L^toIHzulI8eijj^%V}?{BT4@!f_`F2 zEn@zHF=RM==_TBSTtP2;EySGT`0m+{LDc`Ke%j9P}lb_ z0zQx(R^k9m2yA%kQ-6oNe^+$$V%Pc<8whrAAw2($zT?1><6XmuN6n zw1^szuTtTIIV|5^tpCIlmrH;6_L;FlO~<{58!fiBS%-o0$Z*c5Mp9b4<8$mO{b6gW z-NxoF)pX7?WPVY826I$~367EkoK}0u`&5s=+!}FJnp~{wN_hp1zF7!7?d?|dkwgk` z%U<&*VZn&%iNU?=T0u`pU+JoBj9>@VNkrlpmpXjcc6oo<01>hLHvk&T7!xY^Ps1XI zXh)S|c`^TC!`vq?75B1YgwUF_?S=G|Nu znh?=v=TCcY&ULcZMlr7bsK7ad0hyj4zGSi3#DP{v4u&^k9-^oIxRG^~;Q zMMZ^!h&#sRB!cRIyi@yl(!_VZXtUfn4`hk`cVj%bHQxnp<|x)H%Fh_TlTeF>-+nwB z%w|OJM~8{f4{Z+{pf-U18Ge@g60jTjiKkNAZKkv0OA3=WOZSH1mDLqRo;~;!JTjiIIAMIb7lphC zenF9Pc>Wb}M*WL?pDg^AI#?1uSU4YD0hv#!D?VdHs+o(gzF37UjuDtnVWfIy^6lqG zx`PW~>lCGalaQU!z+9BSc8hBMQxc^BtBJWfD{}nzBm^ACYj|+&zx*B#sGG$5>x#So zo_v90e!)Vr{*UEF0|z_Nl{fP5=>?Foo@sCvFkygB#0db5kRRF?mDTrMCCC+sB^AYn zd{18<=lt0@fy}L@Sz!?T4CHb1^q;vvd*yckK#35o#5{Ok3_1nk%5nW>Ocii&OBhGl zB7sL^VrVsxj62lgb>4$pqEThyGNmXvA1_H_p6~j6P+T_g+jgo*k<+L@E`K*};~Mx< zrYJk%N}Tu|%o{&onz?~mBp5oU@j|ytjUT|3)?Wm1;K;u$n`%#ebYkl2TCQ>#wl0jc`b6 zc;9<a?$F+kE~}va;U~h_SDg00w9(@828GTjoLEvn*@DX)+1J z$J{YJnALKOE{+YXG97iv1p#=)e!`f;a;EyQtZgMJPvGJ4sA{xvG@Z|&8#Mc}^*3Sp zrlfAg0)lN6Uz^=8weI0by~apt*{*S$MZrDk5JDH&A2oYE6SQ!AunvQ36 zeV2J%Ppp1e*QPq3t}Jt|dR>BIVj3yoDnkMHH%5EJ)C8On_nW|3J1mO)yKTHH;>Bw7 z&1N(Hbs(hhj$&iLN?pf^q1tz&-~-W~3J_ z0P@Ljp(J4k0Du$`A)m`1zS-Mx(%lTpJULr*zDF7CD1n}6{<_*JOog}32-H7-dk9nvy$H~2^CXGEl7m3S%b*S4ME35npC1SJk4@%w_|B-kaR21<-si|l_f{D7P3|LgkBWWdchfniu8ffs&kFWS zHJE$AF(QJdMkX=BoQVgbbQ~`b^}qCeqM}FlKVvX{qgwnsNLYsgjK)_Ms)h?tMPWfm zhA$kSs)3ZsW`Xp2>EY&V4@BrKEFg+_5y)ysLP`;k$p3%iliV&oo2B}cEu8z`?#lo; zV{9VU{&*ey!F_;`cpO@}E=ZUPoUO~N3R8rwNQLmN-|4m;7OkFAhEi43G+t}csG?ZA zsdm|EQkIZX?{`?ON+>XwaR|C)@9Vj?078fT?+;t)D?sSdMzuf%?+2@Q45hMZx0?57 zc+IU~NnRyexgJRl-QMqJaaCjS#9TDo4)BmNwOB9K$|?QveSKlPB;6%@+&&cBh~%Gx z9PNKq=DsiRZtX|QxTA9!)Y7(O-v!8`PW}Ds7!87Ij0D1b2-eOv-Y+mbD$$<9R|-5o zUY-M1+MjiDv)isLjRkw%F1u#9de3N>;_s4G z9-=UO+-gUkmXPuf_e5amdgNb5I zl!RrqYJ0xg17No%=wp?wLu=_S z^llye>fM?*Azyim1&_O|zWSBKk-?|3m}y6qR=`8zuP}>lNwe z-!xiCX=Qf9L+m1gjM&mxk7nT%hlGFN!4Z` zA1tFeg2MICouoxu5a_4m0L!E!h7J~|Bi@Lx%?79_Bb)=Erf{D&eqcBPw#detqgdjs zHWZEYM3mO}*XLb`JL3b=OKL}hsOG%KVaahfmi!0TjHZ*u;`48i&_D<>OOmpQO7M6O z2S7b$jM`Q>;LJe&L?VE&LIL~J=3l{5eC`1i=nD+z00$gq402-Qzvk%rhkRhjcl{W^ zAUv!J2L%v0NjRwF6e1vrf+YdvWVc z`N`DfTlGGGmulTFcN$pTmH@HG&Vqew+y|191WvMF{_|y6xuZq>kl_7RLW&NBcI@kr zV4^wB2le&>iaY59>Yh$Y+TRorV1R&uZ_yQ`C~tfJOp$CFZ^jz}NT3S9f_=5iE}DgS zffmRORS*~3B7xwl82k&JAXapWvt+3s@rIcx-VJxI2cq$BuL)9tg*Qa|iIQUw38{Le zdmQ}gQ4P+X4-*-q%`w!$?)8>B3w7{*yr}_L$Sk#drWFte-Ip>2w|y8 zu__BwT4+ey%R@04_Re3Pzs7TDLQiW0z>8t`we(owGKf5N1@WGT6zpz%D);vDfTo}R z{`o0fARVLQ@v$cKeg=T_j+C4$*#gCHT0Ovs-tgZwLaqfkAOVJE6aC$T9&kZu2)$kF znEeSTk#U+pdUCXEp3($bA>sk8pwU_x|1B6WybR6FpDTdLDzpQwklfCk_aR3HkxrKg zn66cU3Bdr&M!P+*>@#q|0}N=P00nLC*LT>A=Hk^T0|YeOL$djsF{>lsXT?=<58@lr z{+-+PP|`*#@AJMZ4amj{1#wnFu9{qq>6}xUX%}!{ zcw&GUx&g}#q&~d;Z>t_aTc8|X6`q($rA^eIBrKecrdHs2*}i!Xi0OFxiI$}ey`1w#SP;1@ z!!*5!XyvZ7>BIt_#4UT$oAUaAp>D~*dZD@k;=`O$=N>?o!S4k9R|YT92Wk>!U0;`ip6~ zP;D*)g8n8c2SN2G{NiXz7}9pZ*OI^)egf{-X#YA(E_1lTt6Q|;!^Lq2bUQ6>BS5fp z)JL|UE{OgvI|p;m#BVjl3|23@?Dv%3E((;^yT91B;tgCQvy{@L1}w80LcPCkR*2Xt zNDFNzemMeUXs7i!S*~Sv>T1oOpRmOQktc%l)yi~^*-2M@U%e$K;!f3cy^X1oe(*RJ zT$W~e9K6RZ3^^n9zEZ^fG!MXYEnToDB#4X)Ll91{exMGx`S2J*g@L2$`&wsn?Aiby z9>;@5TTEY7%AW~ zl_7rOZVAG%eftcA z{Da*bbMePtQ~rx`!}8sex4L*?obm3JJL;7VR0uEBzrR2#2K}gj=wJ%(S_53i0d7?h z03P+C!dj;yTwUu3%osp+(ChcP{}8y3pC}$m5Vt>@uhC0>H*5bOgHnty${Z z8^c%ulmCFtv>hiIIuInoHI2>JfIkx#fvdO$LX4(12^oNyMVF?MClAjq#!Ce=Wa z$X;A#(f+jMw)Qhq%ap>eUteo}d)lKm#;+)RY&$G%(&C02^#sCYgtMm|fUL+N)EOpF zK?(O0<~mT-(OrIz&eRzF!p4U&RssP2(?^Iyr`pszVg1 z&`KDe*c45=T>!o7m3yTIsb#PT z!JVE8e=V>eJC9^k4tMU<5!W%ws`42!ctiI3qDc3aw6ma*?{-);jk=$Qv&q_xS@yhxv$Y`p0&_KjQkf+!&&(0BKtKQ z70Bpu?|?-qxm9|`A$tbCMWOo`5a*(StWoZSY~2s3mO(0Q&IeN!U*rX*f7(Wu1qzO2 z@Xgw^J-g8G?Zi%wLg0_MQk-C=A-V^5PBK$5#A=j)WST)BhtKq;f^7bJT#}T>yj-04 z?yL)~1gJ^MkrkMZW-=O*ZgYQU{{`B2IbN7XIDBv_ArkBNGjuyccWf4^-4j~@q%}Ze z>C>pQS=Q2xqlo0LYJCDS35J;0IopV{;;Z)u0TiY>pzbkg9(a7r3&bf!K6Z92s)gt zMWvRP5(UmS;qo&><>>;4is``AFlQ{!xAn1jL`Vcgm;%ky^0F4R$n$EnXD%A zrCoZk)#iZRJZAi!K4aJ$#lmmeeE7q*b)JCB=7`@u(fF+LyjGwAIFhODj#3~wA~S;c zr^^vDS+^q3U;^6kPNzg#kIO~wv}OSowe6A@71;c5lTZK?wGERtx)JtrOG7`xH%-?c z{=vnSI6D72qiL%F09pge$lFgR7X0TB<&`<44LxjvuzSAA)%JC~1&id|;^0X5$j?E) zMCyiO>qo>c(s|xSOp)kZ^G9Ph(#1Yf-{v2Qdtv~J+dw<40vzTL7;v{;4f;atq!^fI zX&pMb&fdlLpkWJ*^7^zsSToV2+5KBE`gtWlx@-W|HkQIilzys@XXUr@FN0?Ai*@aM zZ&H_Gsb-yxRlu3?XAjAW9RMS+8yrqW&yK*wNum3@-3}ztYpawsUqm2(fBiKEa<9tm&dK#{XgDB3bLxEZ_1az`kqKckOVR0@{7c5m6O4cC; z8&)GBZ01xIq}j>LnF(2Sx4ENBdl48WAr_0D)iz-1RpyZLD^pEP=1L&BYA4>$w!Lht ze!t@jv}*xSb#N2}zC;OT7S|O;oMC?Q69-89zPOvW?>^rOhd3!|$XOqF-e{xQZE_0Q zKIHq+J*Sd;p)bE#zVEua2i@-PDD*ILm>`TU)X&Y1DyiPdq1vf?CfO%;DU?e@y5v%< z@l<>`jIs4hLTT?~$J@R=sAqaOm!i{(14M=+R8kHJz+88^6<0uAze^GP(*d+gJf73#7~KeB@&;rTChe1B zNSOs9%+Hz{4L~Zm%KSht5q;I77DLz=D-Ztlj4%jcMBtam@(w^t*CE3z!UUEZL6Lp+ zyXQP?st_noeJgMV0DBGKHcRNT?fn(e>i&>W79j~B*B-;K`W%=J!u(JeI?b~{IlL(a z#Kfv2=*}ySkF&lEuwTPx5E6X$U1yg_kgKA$qy+I_#w(JRpLCs(K;-0xP-LL?GYZ_} zIOulGa@#=AOFqGHpHkY<@ zkPattT7&okNC8cyCvC4UE)&u;_cn(Rf{7>&sm--hh8)R~H`nmLBW$LaX)@?R#Fb}~ zmUIYAs1^fl(ZXP^50Cptiq?I`te2&({sGkf(v+~*e`;x{Om`idYXbdjfoMZAh)9XC zVSsHHe+$@;QHUrpa0^`+LJ> zwf&!S@A-J2``m8|6U^Rgz3Y8{HHc~tv21!IoV&1T7kQ{|_^b^a$f6q`-^GbdS-g{Q zd!9fk%!l+3-v*=LjB78IZQtuM<3_h|pnKcfj(fmA(C2&r2IdC?;z)I&MT~dBd~}I} zU@tI;`ArcmGEFE}n6~6dSbg4;N)N{(sLK=gpMIY0sJHca;}S@Q;x?6@7ul{x-1S!y z)=JJD<`oNw&c8`aP9KH|xrjrfUo19%s$NDsPUuH~TE|aEm+lfEQn(0Br*GEZC2WDk z=#jVaE9@?K>dT9=KHdYVY(rhoX-ox_g>&4&@j3%F-(&7VbuNoC#pOd) z(4=Z}@lFi!YOe!~Zz~8wsG$9u$BjX&Tn7e9_4)}@|L=LhH@@|`>yNH?0plh*l#4du z+D)h+)L}lIjvZ?JZ>J><*1>iGG_?~AR?u|?#9d*&WT^AM+^(Misty6E*KW{Jk-`@K z5LA8TY$4Y|XhYO}7nl)3>-j1F{sTllgEtdCU{MWai4#!+CsGdeO5!O?G}mUqrX3MnHi{8Kp*m=e%39v`MURK?&FuqCazyeya1zPG*joe{kf#v zZQlr~FJ>+F8(1TnmqAP-g`EvB|Htw}FJA^O0n?AOP z1_esAP(fk~Ag%leyi5c@ySAe55%^4)czZHl0cFqB(%0BBfWqm4L3!;dF_DFvlpAif z(`4n_O`Pi@p2X^Ux%|HzA{jLV&r@IiD2&JkEEGh#MTXq7r5CeIOd(x_#@teX9()C} zmQXY-mUM9&C;_$x#QMK<#qRasV^ScPVeX8h=8TN{fG`$GNOSl37`;XzaM6#hywL$O zfmb{)-2cOZa-k9()*6L}iukNs(quBGUiCbCaJ6ERo)5GJ}hrZzO{XMt;qZK z-aR)W6Al||8CuA*^G-};^D_M<;rv5Jv33BgZcra;wlj?jUJth z^?DwufScs55K=s>jBo0*44BBMK(H8F8z9xy3Aj*=Sc#%rmEkRbfZX8@LxX!XI5ES_ zf=k1WDJ(2MaOo8wPQPYM*wVpmFm8|)ac(@n1WDKMQY?WyXd8%isv)|yESk0_F5@-n z^k-cTg;Jlg?&uit_l>bn<&-JIfJaBHS#{*lf)m?JK5nJ z*Cwq2jsEa{{)NE92a-X^8AVG7tKkhgp<03hQuvG=FJ-1Lp`(P9GBRn$$}agesY0P}-%G6J1;&Y~-_F)A`A zp-EUyMcgOfXJ~&j-+&aaiUt7T zr&!$^Y6gP04F>h^h@}j)ixKSWa2ITJSG*`{zmL*G3{T=*h)2_noc>zw+2#k<`D^~g z&acbL%tUUCm)Wo7dgnDW!?Lk$AU0&TNdhM{M;ba4B3}i&IY%&d4tmN~ujL1~GI&TF z?h*1?f5qC}$9$R(cxLWaynaiBWb`w4Td7P&2URr63ca#v%-#TDWon^|+Ug{lHfz{cS>DkqhWDgsafpVp30j?z-Hvmza$W*7_5g2DQY%(H>+y<-g~j zOrEkh$kXO<_~*Ndo@(y_CHSZatjuopL|mQ&W3!<1Rdou&;iRLYn|w;QsKh+bF|m{! zucT;*RFD=f(d6h9`)sV#GIvq+a0#%lZL!$GUTV_`*ANl1nHMgQy;R@NTLz%ftZUTZ zx`G??hCE%QoJtBhc_k!;*lYcSzQkxxBdn}gym6_JYc1_CRjv3U!(A~&dCtK-Bh>Z^ z0F;gQDgX%+eVm~b=SG%w7C;q!QHZ3zzsR&q(}Q=dT-=Z z6RG>J=+JK#>Gpwuwz}aGy6*2mn16T%5GK!4&->k_5_N1|~ z*izS1pGF4 zxxGGZ?!UA3W4F6KK`Ci7k%Spd`R3ja*Iv;`b3%L=h1{LLXGYf1Wld{t4<#XL?|;co1XcnF_gJ$c|JH5)=YPhlNRs$qb%(#kIU5}l!PV;B9MLJl*A z_(R9i&-795fxlxBk@Q7(e9vz{sTd~w$yS_W3E^DY?>fSJX5Nc+`v9DyDd?$WA@*91 zd%OzMVA0oDY}DbbW&#A|3!H#T ztV1Z0NR$x~A@A0o{aO)qTSf%=P=ck}x$SzKux{6=0T&TA-RPWQRTCR=8MT&B-#AHlh%Z$4ucW7gc$Ch2Rz_+^D2wM^&8yxRoe{ z@+!%(c*tEzUWzX+luz!6+#{ZErlCnln8!hfwsLP)urdZpXZKoj>+p{UGG%tl!s zaA2DFcq`8w5ggDNOOr)Lxh4|vnp`Z-9L$UErv3&LW^Nchuh)g@Bw}_Bbiba3t#En* zDmr1@oBIwg^C1Ca}Z*onlB zp%y7b7}c}C1xR)L9;-rTxDVUFYK++PjqZ00<1@78k_I9D9ylEh<>r$@e8e&H|l=Qn) zaVg#fA-$N1c{*bcnolj+x~%0JfYVWwjFS_8%L^me$3=N&|4&84_5Q@hrRuk-SVrx5 zpg-~^jb{8}85wi`9VanSpf%c`P`1lTy)wf_zscvxmWB9HuO@joC@~lb)2&NeiWQPr zU+o>3}7Qpl|0qXK4{I}lK z{@F0ec1ya4NstF7H5Y#a6Y1!N9cvtY)1ER>9PG=pRQ|5oP>&!XTe9<2?MbJWDU@i zFo32gU@Fi3Gv!BD9#cU=1=tDtC9-5ysq45PC93 zm>BiX(xPO^Oms_|O(IWdN<^BJ@&?HaY4^0Xq;)!QuzV_MZM7j1}~GCt;HO0_zZQW75Q0+6Zbpj-C#wC#4=x}H^~N9Zw}Lcl>E7pJI1QGCER zCqXqMqkS64LM?6j?fyKh{~0CPA-hTD>Oil1Xw<=sn7S7NTt4|W5$9F}f}58aQ^|0_6#|Q~P|!t?PVRm79Z?j^#ws$s79%W5 znJ7tq$H)z26$K99W)4OgJsAR^hAyG$JyT6yg$9(+S!)?ogjZg`L4W3g}g={NlLluf{bgyh&2QD}46@Un&{ zMp0$GovdWAz%Ip0cw?iDAm#f*w+v(FQ4rJ2Ra8^~& z^a=~@JOyBr^x2pVUE&u=$1{Wv+I{ehw_qi6*APw|L%hisXeoQGkGX<3y^9AOw&$LbE}AsByiK{71`9KHXr(WSVH;3E-UI94#fLVO%AfE za@_{lP5?yy>uch5m!u365L3huGE$3T41_B=G;i0%nusS`fve;>&-0edRA0ZFPEV-D zbt#5rT67n=eDBA8^`|b1wRvy@fbXhJ_$#>#^O579Z&^L)ivP8hJJks);?hsR-r=YK zat*%m8&H22>ynl%R~46gUR(7F%==i?<5}o^(qgLn?W|K~_zPI|2o&;yeoxohmjTl3 z#%k1iL*6F?>opnmqbjG1dVr2GpHY*!17hc zEAC4h_yFUfz5xniX9Dq~Lv_m30NRitD;0ysEEG*G0dqcO- z4EhOqd~Hufm>e_^A{1Cj2u+)Q17Dc_7MVr>V5lO=oC>i*#+24q0B_`JabGVQJ}$I~ zATIUX9LIkxx82j53#8L8tdwZpX363UcLQhJpAE)3yr;4Y2pJ;s`Ii5xSU?&0ts(c6 znb0&rZvS+*?RNfaqrvrlecNAhFISHvHX2C&BoS}NWJ*k|1oQxatT2dq_W3h7KVS^B z8LV+n@EuhUf>D?%CM0Mi;G}5|3;AZv-~GX0o(0+~mGBYS-p&WkCS}kW2I&@}ury4d zNx2f5l*fHG?Z8X*SwQ7L%x43Ni;0K;uTt4#^bAr?;X{-1Vu$twcoZuqcvJ-ce3K#A zP(X1<=!H*^*96rI3vj{X*L_l!MNAPHa%zma^c9|bC9L}<(~V$av(mDTnP%)AV9GGI z%oXu;^Q|II`vIx;*fD`>ugcP;bkDHQLxEk(Ei%!BAY0u3pH>$V5)}Pa>gTWSXU=fIouwHctyU-x2C z{(1Kk!$~ZW9~j7HV`nD>!TK!KXq9Mz>Kreqa~znx%AX<Ap4Q-&JSn-yi}kH&`w zv3>8Hy2xbh{4Df7w`3WV&!Q-x{`&vAqDK47iP?VSa}PZli{@^@!^KnhY!sSTF0i*A)8ay>cjhE7}H#Yn*1%ZUb3Jl+u1-KKYZcYm6wlf%H4At_ zH(ooB`+;#{UNWyJx=RU<-m60!JS_qIv1tjeSw^&xuajegYk{fdQx-9EN5It^N1eWw z8q)b)aNtdD#|;Bj;1u&LAA^8W1Zn>not^fSkPCHDSGZsz|{!9H#i2 zK8A#b{v}9WL-6=z0{lCb_pAk&Bh|CSPjsfAk<)4Rf&0fGb}?^tV!~J>{n2W+!Bst% za(@okbVPW=fxc#%)O{Cz0jvct0W<7P@W3EwP5d`Qg4k#pcI@eWQQzw*xd*R57X6gy zQBKy7ydKl1fdr$5mnYkE)BDH8n`+?9yZZzJ^-%C6Jz@)CJSM$^&%g8Mxg!Zh7Vl(5 zEsy#1bM`JTS_!pM1qZR`1KGJZ?TaKl60VTL4An|0m@OHp=LSpq5! z!dX=vwVY_vN)4=&!-~o2%d#luEOpNo{&$>Rv zvONSpxbt{nwn+(DAA)I|@x~jr{?=+9?-Msp^e_$DH;u7QnU5^5^m*q2wy zg<;;qUBj!;(bQ>#(vwy!6pnCEu<8HuyDrH=Lj5`W_7K$g?zXd~*rJv{#;Grn5%PE8 z-vU?Dp5=Iu5eV#m=vu*Fdjt9^Y0Ie8{#X=1w9y8R5Q&@5%t=|>NlD(RonWgj$qQ! zq=U3Y*l~#&f-!sle3y42vG4tpvy9D+FI=5Qw-_$xJLMUgSwPr1Sb9*CsWGf4&I<~$l4VKfT5 z6O5pWnL_T-|NEy{L;cZ#$J)ZFIdB#VPi}tmG(hAEm;SV41MBpqr-1b0!BOyk{D5$U z20$S5OB7oH_rRBT@gnT$hnFGf_?3H`z-V7roaZ;7JSe0;A9N;>K>nx);`DA^!%s=g z0)8ld@SO9UXk0O*xTk2<3l5-IlajU_&>YPH05`klLw@khlp+X{UL7b}O{S7NS_15N zT|AYjA?QKNYG$_qXBxk6($P1EjtR=6#<-j`%}*XG29c|&dy8c-#etu(hM|iGh2nR+y~9CTHfVPwFL*C(tm=J6ZMzs zgIUsYb@W{7<_MC50tkOmaqn`stsX)r>gN6IH$l_&N!PLI?}zv4N;)CfmF{apPFs+R zP4*l461BMB5#|&lIZ*Ikj}dx+6Vll8is%&TKvPHyseq`=pz!%!zkIPR7(s9y;M7|7 zmwS7~Y9SCf2o$>0;b0)}6LBV#>Gr1(@p!>Y7x6Hs|3ae?7%0gLamU;{?vPG`khR&r zMJ`MP^@8_YU)%yA(CcGtBE=QDLf;nQwo_@QyDIn+F0$ zkvxT&rziU1o#pV;onh&S=;qW)(A0W^SO&CW&F;oTXCN9grdo7!XoK<%`k69>oT&>> z>Xze0ry=M4z4R-ImRlgXxYXdJufIdLXyL{&h_fF8tY^Zms7~UIxkvYJzDc4W>VYVs zIhgw9FKr|^7n_0&gR`3eh3pS(e~^oD|5t;zb-xqvfHs4drc{!NztXny2_5??`3p2e z#-`hlBabTfHl_3y*cD$NhBbTd?l6Y{17@Ruuq_ZZ@6bpZ)5t}%G8TykoVhID4+f{@ zBE3`gKgQUx>g)X~tEqJ?IYmX3LRo^8eI;vFEM3rYQ(4X?T4sxQ+QpJbee{yosd@>jx|9ih0ZXyj zcz_LgzBO6Z!{r!zpNo=u*3?~v;Cycw#1Y$yB)qQfrlIQxqN55julL6^e4!pM(Raxs zD3*|8{f+w~DbRd!?7juc_2Z>Zi!$ZkLX6U8SLah3SY$GKvpZjM`x=;|znHf8RdvCI zCKA6X;}~3lK{2w%XmalW*g=Ws(_FIQL`(M()}Y7W@dudr90r;%vE35Y9r_*orQRGk zrbt0%MwXRmE9GS}xv4NQ=I=WOuHcXaQkHKlt))KfK76J>lQL-uZ1xh*d%63C>Vx`9 zu!$+^dm#D^ytQz3M6`J0QyOaV+eDw%d7*rxm(gj#W3mL|V>E8NTM6}}7sF*d)b~w4 z)<1du;QTw@Ja#U8g7L|#ea)mwAaqJ;#ut0+3~rq_!EA(!qfb3xY~C|C@Av^pRYv9k z!SdjwOr^#05UUuos?$gGh?py&q3|kpnIP1N9*gmD1MXF-zdvYti1%%1c<}2o~I}%&v92;vlT@>AUETXqR)7`eC2%DUbyZh7f>kI5)-=)=yA8SWeccrzl zo@CEr`&e22ArTljL`jKBOnW58Y9sSXFgiCXTP%Emyw7XKk<^TFbvW+JZtwsLiInu$ zO7|Cu=TQskB+L1)R-Zwh>f30bo+x85jF&FGvVs`A9hwv-x9*(%^)rP9FLJ&P6`NJ5 zNui9G&@{ZO@MT`bYiPo zT67LQkrY^;yr442HsG5IW1(id%w)vYsH&!y=q4-&IvtaDR1d=)_6M*Nq`D!KdkXA0 zf<<{JAX9OjfIxM#f}r9YdkMt2s0jTDI%gu*0bTfZ+@qmN$k_6AFXq>m&)uSwHxG!o z=9cMLm$z65&GdGk6D_J8aKVCOaMTbJzu6Cmwrg1~8C~87!V2kCLo#50FEurkisa0E zGBjnrtP9ri%T-UGK)V!SRk}@j_+h!}Vx+NsY*;IQ8vZw4~&X|JP~fozYATUvp!FlS!)t;R>;zK04#a zIvy=Rqxap_GT;$2<_41bX#mhX&mX zgLN)y;9XajOJh`9k=^;-*2duAW}V3A0dN{GAnb1JK9GpwrCK&V;7M`GJIdtHD~&!D z%)z2ZZsWj%=tu?DlF`zNB*`$M+^3$qU0vl?rtW)`<{Y}O-Lo=u?@Kh zHo-Urg;^y%#P9=}>ISh6Yolh+i{;kQPe;QUEE|f7!J+$3r63$h_EMBipp*7JdAIUp zL_nXS>f(=-igVBzdiSS7Uak6k2Ok8b;wV9qHuW9yzSNv?7#_SQR4PkRQ8C}H5h!Mj zDY7sdMGLr?aS#vIPt%^6{*}XrW6`41#vG*de@u&v0Fpaa`hrBodkReJKcNIK>cO0t@ow3YSk_h=y3SMKReII2Zi*?wAunleJXdG4!Yvc%~!8Kf| zKw?Zrv+9X)$TbrFn3nDaKnXj{@apBHWa8lm2h1$|DHxaQ94ksP7o!7?KuyN<>Too8 zBRuC*tdInem8xd+{Q~E{T$tVCfOw5`v+3i_26!|CJHX=M7;z5c;NaXTYTQ%*(cks1 zr|SuKEWEw-a))A5oYxVSe8y!F<`U+4H=>KaDrHH4)^n-#c!DDiu0?AaKSq3ieBJ8n z-F=q}WukzJHib*p4}0qC%&KobrG`hV5UsuEUisds%&5wzlFsRRjep8xYQwyvb^H|4 z_uh?>bD5-F2PwkyFVRND(~lOnWyXC_0z{L25CL5T`>f%0wD*}chpI4W;6*jGE3kZ?h|_)!m(#*~8Kg+FTh z_8>dw5F2b(3kDPPfbUt9{w^>JZ<=-|d;&>qa(az}zw0Rg}nI!75j|C|^yL(zYP@IH*+*wWf!#Fp7jytnW3p zoThVqB}ZuNi_o>oAyzL*Z-*Y(%aBEX{LpMlvFisCCE}yI5Q9OMi(?t;W=ofP)3(z} z3ON%Ky~jjtYaP~26I+|Wf69u7nv=TssL+Syea+#ZyD_zw@5o?#V@Lbwqfe5da;gq<})-p`cvg9}{RJ1xOOi5sz13#Fe3?0MqZ6 z(5C5sRAVX>yGJhdlkHz&b$|*h=7!xrx=|Ao>~$Lywc>w;wHk8VP<$-;M>$H712iWC z^>Hr!zrqTUq5t#E+B`VXUu22N(<8Iwj2y8;UqE3Fh0C%MuZ@9o?Ns@{^YdP@`>Ml@ zU~6_teqoS_W&yma!ci<7XmY-@5t&QOv6(RQ+Zhm1>H?%)$;Izy`g-`-|CXr9xTsekM1iA>eIWL!blzEnMuX$51umMs`iMv zJwM(3{X3F?#x;&#=_C~6T!3KzCzK}@j0;GwZqNUYq5FY#U`L#% z#5fdN3{ff~mh+(B+y<#GRZu<*p}+F{U_G{1GS7>mhD;wb=ss6|HQkong9aL)l?Zpykccx@IuUIxk#Rvv0^{UQ`C z>c=kxi9P86~gj5ecu@s@xKC-anr7@VI^7+;yotW{6lJgK+pwgV3(xYgbY_ zh_Uj-xJRT!RT7u>Egi;V>I`BJ%RuN_mHjFz9g$5;w=dxx@cdQxNqx3X95Bg$^q-7A z5TzEa+67+V#?G_}6DtrKc>w=s{2p_Ot4);iIk&*!u^bW$IC|2@m?TsoNgZVC3465( z3_h+ZXFe$8_m92~evsH<2Ey13C>w?QwO-`q8*s0w>6!f!^^=91=@m1#0&qn+KW+{> z0ix@mRGbX#B{q7^s~i5WDLSe^fi4C5%Q*ro*lr)_B0iD<+eJAUrLGDk8YmyNwJ(0q zJ5@+PFf%piATqGTa{_<#DxGT+DSX*e{Bvm)aFQQtbtbtZBBH^xP>izt6D&wh$%=|5kJ1VFD$Lr zBo~THse!hUz1XW`%&baCq^jw)KMun5L~pMSkH0t(M1ycM@EU+pF@F~mjTi?Vygfjc zsb_1@nM=3yluX>CLJbM5N_H;wjCofLnc(8Q*;FZtl#|%L*-D6J{VuV}b@R`2g zNVdjyz5*1btKHg4^*;nM7((8KJ`^!BO-aU#@=ClL4^t2a=C=A>096Xep+PQFiNh#& z&}2Cj3qUu80%~O_m6Jgea(km*b_cBoj`~rzB>io3^xNX-S2%Yc&I|Q48eXgs0@|;S z=ij3>#5VA$M92t8pK{q!od605@{^6%JDW{dDK-L69vJ@Wg-8GRK;}3=7I?@}cMNJ} zfOlhM0sCKH9ff1lLxu`)A@wFe5$VJP+g{N94T3Mcz_8T(+~A$K{Wzy6pn7L*Q@?`@ z|5X`Qr>K8P5zinTwBO~Ra@YuLH|&_b5JG;pBdTTH{=W>8rHcSaeM4_AX%3ca8Upb2 z9N3cqAJa1*%NZvVN+@|Diwpo;N8#uNZ`UKBo{oKcD%j z7rO1NV7a1E`Iyv!71{_nS5JFX#UY=M6zHc(*V{L%Ay!WuT#-h>=NnbvQFlO`Ub7UI zX$BN~vI7>^Pz$ei0#qe5!K3bo>@_)nJL?AJzsU7E++3ZjXVOyfhJl!kuLm{?N7Z9o z(2WlbsXk6aM-E8voA8E(-TB4C;4-X0$69m(@x13}%VwYDmBGl&rv)8A zfBy&J_f#*c?_b;o1T#k`%mKVIwQh2!hr-zb3T*{T>UV!M^3I@6bC%NU=fO z2pfvcrHetg7evbd%U<61Ox~_^ZWB9@qY3Qjz=Z1lnSZL4xfW6gPXXbEiNGwM*Zo(I zxQx;{>qOoEs6v|cR}rF`8qOew1+akrkwXk}Tu@0p1qv0aMP5WHwiP4sjLk6?!F^HB zjeE_>-vxiq`kidO1mJ4)HsI9{jm1RkWGSGJND2HvYJApWdxz;hG0@>6YPJu+C z7Sb7l<^4x}SwRq4H))BJREwpxD^rjIv(`pDqf2tbH~pY~YS|1vqw>eN8(=V=1^}W1 zKqOv!zAP!Ls|FCUx;2%o90iE6fF#uQy*%Uo(TyO^$Z6a2zjh!8SR1~4Id~KTk4^v8 z4N{OEbKvdZ`R~$_gG(z$p=lBi*4H_dCmGzU_Y9&J^Pu(h1@+e|XiO5@AT0m?(^Imf zLy!_6v7sJdfjp1!Fw549|B~PygImtt@I)6XtsmeY0Tw!-M%NfcX~tZuB|phVpka6C zC;8r(oepG4FN~A|Hcy9nq;I*=N4eh>gbRd3ObA?G-V z_nNDMP`Xc&NuMFR8b4(VWR1su$HukS39*wv z*INU4)j2AV@0+^~aEcR1@bQX-!y!NLr0PDGVS|;B7u*-}UNrBvy3eShz0ZOSR31P$ z1BTqFc3?)LoH+#gs_DaF$=%d^Sb{_2YC6Op>w{y?5m+oDD`9*=iDC$KCx4#!14u-@ z?DM-wkz0+`2tgHY0<9q+34=>f&ddPonlnNk7H$sbqkdcz2NUSk3^W9(dZIl7|Fjzw zIm=KO%gpIS8*}l>ih>Ere}bRkXiRh{(pERQjxvm7u8z(@{s3WjB1ObIaom@f*k)Z! zpcY9-iSq(;IW2~=%))N)t-n&#Y>=2eH6uOy0T^gR2(oQLaPD)mPJAW;E&z)OY4Auy zdn63R^f+|oy88Dd(Cq3(QG&EUum8l~7Ad7@oqSmS>`wFkO&%=m`0^?oRpPl3zqpbh zP-VbEap~K&#PlNJ&dkWrJ$@c)A;8~`M>{|Jr1drF80__x^xdk`gooJscEQxEgabXS z3aZ(|{hbVVW2{{Ye*I&TLQzVDX~!RS5GCN>;)nB6g7U@|FtM398qpAp# z2QrWz3Ru=qa0M(hhP`rqUYJUgBtaS+JV!!;i1>v zwxa)SS+AfMI1}DR#iFe2*aX+vo44`R3t3Nae>H`FYi!ls z9WBRQu6ymJ&oR)Y7liBbOZV9n5ScidG<%iBG3yqC&GwQWwCif^e7cmQv%oyQ4eF*_ zzco>9>}eom+Z;Xvgr)2GUA+oZM^a;#&_Gb6cT&MxngtM|z$perb=yj^N?h^mKBmR( zGR>_^Bf*PPh}MGA!mex5i>IJS%SQLLrl0HCw@A=4L0@$98U)WAhc}0T4)FN zc?(0g&(e~6Z#w!aX4I4=2dbpQKi~2Qe@_ql1TZyx3d{*K+1g~=c@>uum zz+iotk13s5dV`on-J|@GPdar9yr ziM9}u_do3FR&c(^(*eE$K!G(Nc!4P79S|3|I=M=$eajL4`Q8!1$Q$GZx(Zx50*OYBh0OfSS0p1?beapGin}l1NI9IB zei^C;d`9CuKqtCIcN*Ru>YS61K+#7tkg$s{M0!^2F=H#P1#xrFkoc+bDfKN@a#4=i z838KP$8po3+0gmkwi9bHV`%Gzr+%^ri9til#S$_PNm`!QmR|q#m7)C%b6B^NuPwea z&qF;K(W0+N$&)G8gm@CoKeZ9*k;d7>-C#4u6xnng(r!L(QfO)SX_) zx6j~GNZM=z9B<}p6*#xajH@nJ$;?x-EaFN=L==>OE<=%`v2c{A=u+TQ zID#J-{oDx9=*9q%*$Brafb(h$>`Q)GC9|du#@jk=yyvqZWYvRvns|_D74KTL<+9H7 zD@dzY6?X3~S}^wL^)Gi*!A~W;g>`pyJMs)O2X7It`Xe0nQXr|ZHq55}L;6exkN}rv~znO** zTow*A`CtEXLHbajQWx_7_i4ZmPL9&Zsg~G3#NvN9Uqe~9`cK58)qQtA#!fI2ya2OI zEtCgi8gy=xu}j-WvP>lZb?wII@B56LH);(|8_1!`=90-rp-8KQVUJFW2JCu`yfi>^HE1sc8 z!V5)tiV%iVI5oV@e5OvdGV#P^f>@xxj5_Gdf`#dc8-)icp;Y_flf8-HAVB-((DI~o zTP2A9De4tw{+-xD`nxrS za;A&A)S$DVl?sVWOiWyuyA|JBv`)@ajr`XCE$i0Q-YxI)cqZ%i<`0+&U&mVjTD|F! zw1oZ+ZX3o(hxw<6sT~(MXf`&qs6-3&NV;oDO-;>$2r}Z!Y=ZF@2po)967!^4Pzg3` z@2RM$99J7oT1p$2R)7pMA;B#q|R#9+c_3z1C&ZIR4QpvAN0dF(LN-`+mHBqM_6~A3-omQ0)59c2E)`ktM2H|fxldi6=epR7gV@Wq{8pO&xDBsD3 zR2rg}`sr`LP3`w;d@OSPxyxf$dug}yt-V1hYO)Hg5aZ#|Fk1KIdJw1U4o{>mb=MBE zpPywxC2}DwFppXfMk`%!qJCJ|pnpAkR-(4QX?T2RFpQ3tYdFMx&w|IO?%Q@y-}mon zpR|hyKuU2Sci5)At4V`hb#=9!H5SJMDnz|}xa*^VrKwM2iU=(5VPrb+7lY9nFgJ*J z_20s+^uI9sxHF6~tuW)48lEM-KF&!=dBiF4Gcw)f6Wt3OgF+vPb+G zzseFtzd)<0l&v|pFzAZHYpdipzm_dclmL}&o5K`{*i4D5N**ktmXLMmcaqhj4&Ilr zi5nD1uTdJFwT-WOBRpyV464*rd|>YHu-k@ZWo7-TGo(W2&a4sR3Z!H(*(~f}rt=Wm zvu7}eF`#27hB%`c|NIe75YT+qzVszX##K!rn)j*`@ZbLWSSsW@SYilV#`b|HEJ>M} zWQs?Iu3N^B8}$B&Nu#}%LLpemwo_9uoP0eJqLzk%c+AiL%l4%5vpAQ1KA{+Q;iDJd zMu2&xM>YOs5{T|900`)t>@+4+BA6}Oy)73f@$_5_McP7`W+lVtMgs#P+E5o}sSfFQh(7c(~s*T|INTq7r4PF}Fi1Bdh zjg}oA3dK8OFT%wY4eFvFC_MvSCY>5o{E{^XiT6nJe-=LsCET$BTR$2XZ3H9w`23Kx zNMwMMQ%f6tYXtF;A%exef`)|LaiKQ-Nu`NoaGa>zT=|2tMpk2&lraa6ikJIn|E`Iq znXjY4v)GHJ5+2Fc+ouzV8CdNU=9jvf%FP0ty(cxUjpn&mL|1}#1jG;zpGeCp*R|w z1j-NPu%!>!s}$e)GFfH!wP0+lZUZ&_wBr4o&E4mLviyz#z4n+B*p&&|?j!Z~8HKI4 zKMc`bhK3fdCA)^S5ay;YU?rMnJoFD>&+Be%is~nBX@`y(b|M5rOP-aC`K7-fJxo`P z(Zi9(5Y_qgD>VKdWr|)|GV)a&czv&2S+46QjLDp?y5|&)=_`*Wwm;$oP9AI48Ge8M z+d)ld*vdU`W{+7@M~6|IuX%=kJn|mKqSOtYl8VZsVmpWILRJ2|aA~YO8Hf0iUk9O= z1bP_@tSWL)HKPHl!+Oo1IdFkGoSL7r74QBk*-l9{@!Zuo$$BNeMQTfE9 z-4CoOw&e8tfMV~h;Hn8f&M{GCoeWAAcx{E4ro1H2t&gBXt#Q?^`BD)OXo4f#ZSid7 z!&z{p%&VdAqUPd%B(M=&p??NM)a5;4`%$Splz)zr;dnbkC8Ap*uvqNnQ zeSW_F_RwMX*MQTTtm=2wH|zOKB|on>=svWhlx@$~sz_X{GrTOPPPO=>gviW%(T`lc z-#;*ruFqdClq2KnT7?w5W%@f&(Y7+{nekh`LhqgP-W8jO$YZ98%Do0og9gnyr*q?p zmr`EwVtWe&jPC;d*+e{*)42^ef76H?%6vHr5=3`q3~j=0AHergjM=5_RXO>q5$H=| zBEoK;z?oD!#PHt6SUIp>aQYZD<^9O z*m|0#G>SCXGwYU~GJo3nD#)h4Bsn#;C>96RsKzA}S>=#r%*pm6Y$Va|@vjzLJJva~ zbe@T+jE^yy_>@AlkbT+gYm7!TLBARC$DgyLw%C7W^7(D^YSdgk{{&thr{s&BBLa{+ zvc5jw^#2~G8QDw><;u|1nSKABtysVu%6>fH_w;Yl8at z%9?k*%x<=RYOJ1TJsPt=`*lHSI&|Kj5X|`g{d>2iZtU~(M=9372GaOE`po2eKk!UXRe&W8?|D4Wo>N`yVj*0C-^KpsA~P4=jLpEK@KbW zKpYBPz{xXho7Z96;)QF3iZ^19~N^fR9n5}w}RGd@l^L5vZo`agrZTN1UiTxx4v-~iMu8vo2+BDrdo_}HpjV)tka1`z_%X_?mqvP3gET=f%^H; zmu1H1=~oFvM@q_Zf4=!E36$RI_ekDk-v3#sEq^ey@k_aYv>#E-qAX)sn8Pi?l`VN$ z+N1JvN9I#5!F;e;qo<)tzC^wK?Xkc8yeH1%0bi+@N8k!&4A+$zy_fN1_YOK#=h~YR z79IuZYSLJDcxi4|QVuSv1y=x8nchnisN+78txC~-raW3y8Vm_t2H94jd=@jzhik)a?8E(}qz5Y>*5&y1M1Lx9zxKu+ zf81?8n1}w>MyHgHwrNe7rw_elk2V=y`tKhq~E=(Kj(p##G zlPk{0cd0~l_C9eG5T7qxpIU#LtTJrJ#O)j9&IPlzG6)Trd#ajMcKmmI`}yCzEH)tC zO;*np9n2B_qI>?N9~iz+emW4r7RqV=TOAhC{Xl=9A{7>i_Czo?39D6P>b{nXiWJ$}_k12l!}=d77-mg6 zALa;EGFq8`QwvqjyU|Mg`7RYg`{7fd2O12XvoqJc8FNbRPP;j?AtHGwbV{Kku3&aAz4wNJy%8 z^Dh}$)-GVgXXkY5F8h;I({-NbrMi!P-MzeNd}bcnHTtA?y4FbWt{0aw=+z`(0VSI+ zrd;iE@1-`F#_zk@m#M%v5bM@|bGCkmR~ur_w#THV>YU21FnorQr4>v39B`acPzwwn=nv8RZ(0H)#;bn&$bln+i_NH+ksN>>X z6-Q^i+Hcw*Sxus32N3ivrEe+t5NMtjLeFQ`^(kd!_>97rd21q zZ!VFJ-!pfb{@2z$j&gEpssRqsUtvDgnq~LV_*dgICsU);Ut2QsUf(g+le5x`+_U4F z^YO{A7Rvm2vDodd{@mRq7pJ8i_nSLqb?OGc?BCyVv)qnm?A@REw<@>u{9N1HZ|}R= ziB8vk^5vz{-NKaTDW@NWi=A{#-RrdGeqHs{b>AD-=$uz#{kvoCtf?ROz2_6>d0ZX+ z^UwL!?dzBO&z~0g|96v2@Z4J`e#;k>_t{SIZr7W*z?{>#K&i3Mb7s+xLw@^LiCxx- zE81nJ@Nr{j-QD{$%#R*BmN9?*#(BQCVyApKxOQXm@3NQc-4q@;%DF`<@JQK2tWh@b zk$Ek4_=3QiJoe(ft)I3k?bi&hSDid>p2A|c8vppFQtRq>HlVYciY~{LhtH^}c)_u{ z@{2S7%;2iswYSY=*~PY*9`I!@Ke2oD{fTq#-&f_g{j=fEzn?RIG4D596U;J&wRG0M zJ0=IK);yN0^(hT#{d8l;#&=Ja{m*LyT?*vIng+si`dR{a3|88v^mt-m_+*v?PEpYr~l&T6&) zzt8S&)YpmmCBM#FUH)XVv-W!4%QZSDb~UXxx>~w_|MLfBI|?4|5xQjYx8U^sihp<7 z6{{l>^euNzy&d&MJx<}f!g>u;&WKGy4(A&Jjb50Xx!w1}w9#+%)+)oJB@Xin_sIUv zQqC`YWz8>Nwe!>e!+%?*r>@CU7oIM*P4S>Er%8ju>>njBr(O#GHvjG$)37O@EbfWS zRd^b@^i_J@*6Y8W9y00J{@B(ms9;yd8ee(PH<`EMxA7DvtKMH$d|YK3TP02lg|Ymz zjqTkKaQ^wXxu@5rW~v`u>b0NmyH`+-^v$B8wO{;BbFSXCal=B-h9=orZx02vGBQRi z{eSVH^`x86$}HC$OPjB$J!SLL<0{)K=iHh7bH^{w*HwT2oI7{;@B%ZPBnyED8WRgL zRHtn`$a3biJa3?d>mKioIr-lq@3j!K*=RTe!&{fpaWT zYPYO=H6v7ysCd4=lJj!vEqh?+e`_EE15=Twi(|;ejc*iv8pO&t%=x;-Bp4&E$KG1b zCiaspX)CY|e6(hgdg$$I_Z_r)yqNBBUO4paTwC~|9)=dFX{JYZ8D1;lS@P?oa-Eci z$uUL7{Twd$UqpoNFM8;!BGAT?l$>nZ@J6o@6_%mVs_6s7ZpTeej*v7|8 zvrguYRXVuj^p?Z39Cnv!erm0lc~29>gs*KDd#!Q5Y|30vpX9J%ZvAbIh|MmMzwyS4M5oS7lRIe`J#gL=TCaiei_vX2n3E4E=OuooJ3=S&ZaM*|C! zIM>cs9P*uZPmPOqDqPJ%$8Y=@00d{J897@{1T$m+nwjs+v3}lkUe1=%1bNR{F vCa`!MPy`yvm+2AK3}pWVvPZ?y!{ML2yGcmlb7$@u3_#%N>gTe~DWM4fMC3-_ literal 0 HcmV?d00001 diff --git a/resources/images/newRunConfiguration-new.png b/resources/images/newRunConfiguration-new.png new file mode 100644 index 0000000000000000000000000000000000000000..897ac7a36f7f80109dbd6d343d3b5892e85765a8 GIT binary patch literal 31191 zcmeFXbx>U07CqQVpb6GMf=eR-g1fr}NYJ3c-CY~kV8Jawa0%|gT>=D1a0w(xaCf)4 zB;WU5Ud>cZ)ztj?qi#`6bLE_U&)IA3wO5#;ycGIl!p9&G2wg^6;xz~ae+mM@Jq05H z-{|iV#(_Xjlr6-?6=lT5p^A=nrWV#FAdtELZmK(n>VA7)ruSNG_fj(NntO&>AA@m5 zpHYT*a2%~nHg=-1bRLybEV&FDC%wv(w|NOjbjAaA=ezU!`}56vc0XP2Tc^#+)&=%Y zOU(qYd9Q2EeSCF2Z9sXuDOFWU;K!g*R+Pgi++JrlOa;C(P7x5>B1pQU5A6r(U}b$h z+&vp^Cc=iBFx95PLWfny0KH z3=Ndv3Ti-y?@ks4Ntbmxt>om^cWP=ro_Y;;Z;(E6|H-st!HO*<+jm>|ezhX&P3jnD z;-^&tXB<-%n1}#7IZtT$S-Sx5y|RSVv%Bjr|WxSR6&s66_S_F#XT=Bq8{q>l0fYHJ6>w`N14ZSAm?Kw>Ry^# z0`c2BQ3QDXw-r33P_TsmlNO_=S#Zw&SS$!yekArtq#byO0W1*oeIbIpfL18#N^u>K+Y!d76v7kCXRcn0%hz6 zu?1Q~rTP($Ld3H1X|Z0uJriwIgi}FN72zCF-QaU3YC=XAVa}4-KsZ6y6oq0@AtH-` z$o&;1%*pY=Rzd7t$XMZ_;(1UuEGdX&=*ymG670XYe!=}BFob7)ry&AQg(V~Ym~u5% zQyM3aWDJKOAVTURxl_#B{+Gsr)#&cXyg_LqK4MI{EVOjtQE^h6ISfing(51%bm%T% z)rclP%NM6v!HV&Pyc5hE1Ye_*B)7B5M)o!oo!R(MbwY)rZN<)WGP4Ut-{GSL2gml9 z8#1txCWD8VhR9_J*4RGcu=}NSG3Zxmkd`v2ky(Y97~)jEnNgm3HKR2ny2Eis6BUZn zRkS$dkkNpzjZ_YC!S^sO`}G{=(1J0KK^C+SHr%bgG0G@Fk$ z`BP+*phU5PUr<&kR|p-sFF7x1P!lEnKZidHeU_ddl%HY}vx-Wep_-Q1xiy&DrP)8* zf0cZS^GG2!D_Jo)f#W60DxXPmb;k=6Wz!m?cc%P3uCcqMb7=fYIsrc;1VaVmZy7wf zub(`Xd77W9h){H0s5+s$#ep0w9@iaC89@0yH!3&NC@MZ(IdVMF3E2!~UG5tSVH~w+ zO^)Q~kvaOO^-oWk;FyrqS=71I1*f6Y*xY3GSZ*wC80RK?W`!)$6H!kGB0>8oG;-o9WMwkbdM-6OfE<+-3~KXef!&?P+EO*2)+HwEUm?O zsN9G&i`YSfe#jy+d2x)tV#A0-ww4&#W|}jSV7RWte)cfRF{;*Mn#bzkbJU7(>F|b7 z<4|o}_h&C5li283f=si|_-Lr9OzD&8)acJ%6El}TBc=9veG_#N7nB$Dp$9GuH;h2W zR)+q|lP{WISf5uXWUHj9(-C&)v<43G1 zuf_DD{I#t{2GwwkLR>{+rb^cH8Cql7Pqbc2Pn1tohSXbfFJ8&$JbzjA(n2Lg$NimS zu;Yg#?xzHaB8k|E1;xgyPLs})YLo7qZ)){x$1N$hR9v)95w>);wh2=S4+&2R$v8f9 z+;YC+45{V$v{Q>=@pJNp6_HheRlODSw)qCt2FHfiWa4z>L~9{`E=>_$sd_$lK6B3S zM8!xZOBT@uQ5tJ9%M&hRLN&rRR&374Y^|cMXSk>5~xNX^V*+yBv+l*O+ zbJVhYW!>dA;&x)C=kl~+G98OOGT==T}kVfP8ifoG%ngNc)qbG5xLU%pP1b=Y+2jC$8!BVg)A+efP@ zloph%yAMBNX0O1}9iQKte=|SqP37%+@#A>)H1eo*vu~^K#Og%qy7^M?M9*lJl|BU( zP7N*}&dHzJp9aA!Fd`rd*&95C$prQx%OQIWVZ$jV^I$j;Pd3mnm?^N2KlpWU2_6hR z3eA^p?%(Qu^nluyj5T%QBwQ zi#K5oUshk=jqQx(S7%jsj=w0_9(*+5G^qY9D3hS5ve3Ldp^!n~9q$L{Go3`M$#f^p zb<1zZ8N-6@x+Kbi4xNW$3X!IAUnTF}xz~oy_RM0wZ($ZJVlT5QdtXt}Alsbg`AA!) z<>;{ZesUds3SB2sGxBu0ry`L{>4Rfx_FDQ^Cq@HCoHEifgz0+ieamqhtEO!G+$Nod z))ngYuPqp2Ql@>qWeHlS=~d~OwjuKwTSwc3yRQ2_v&$pn3syfp>xWw^t}&Lsl{H_v z&FydgX!gm+)$PXk*bIuuc@jj$*dNt@n*WEI9;7p z&#k~*|FQmYeR-X`jpXXvaqCscY;^gf>$lVIM&FgZ;uUuH(bbsJY^(WIcjUwAj^3>H ziK%t|Z18G&=EX_x3kLR#OZDe|K|~Z(h<EGrIt%j)`H&r!iwXwNJ#6X=ws_?3ZalAFc>se z5AwqL3YjLmT4@8le>r9Or1;E@RN z%k#F{liD|K&u+T@ye;mN9InwdnWynS^2WS0x!gDTh(v`3nQNws$n! z{?7hDlY7?bV(kt+?|VlpjC5gbmpr!pq0yt8qkto$r+xGaY4oMMZ`3F3i)$~`zNC-& zSC5YG5BjP=>D~+9wYPY^|-=eA(|m zT;AWO-3#B`@i%aS3Ilk@YjHrH4XPcQkN4gz-JM%KGNT0LquuBEsi;83$bbXlEG=s@vR_%U}M#0ffxXFyVm7|P}>vZHgNk7cvIL&?(MpDt3E2Q}8< zodjYXAbG*RW3j>}C!|9A(j8&(_`CSLBK}Ykfg-8OV`UT62~_k>fy<{?Z=sYISk+*X z9^4=r3V7;%VhI%4Xl|_AP=_7?Z2uLJm(beSDQP`pVm2IiYOm8bDx`|d=i=^APM^>f|py7v!6{fI*88|f!2$^{8pxexHm0? z_u$bQe^NwZ4_l?~43)J|9qwF+cc4z6!}5gvS%dTsQSGPYIOmV+BMO#O56>>ly_oLc z+c58w{GcN!NQh)&blJ)F=`3OwGAk68*g9b{Jz|FJ4#^D?zo;!@1*D(ny&jVr;~|KV z?Ekm|apY=D`k|0vwxmC5d}u6VRAjtqa@jG^Rou1J+w|@f4Zv-Nw_>ANFr~BC#m}Q@ zg=b*j@vXD1rDjrRdS{e&s&}Gxp6?{?oPTduaxdzgkltdo$}aIflx#76{rK15n$^;WwSpt|i~7U&oh@|~P{u{3m}etY2Wl~N z<_!4E8srxe;Ev(P!r7E!Bw~6S0VicA99Je+4J?u~(me7FuVK=Nj5*}kbdE1q{QH{< zb7+-MlFc(W6jQ#AFkybr(AaKw-^g7f%G(mAk`PhRJc8%RmrTVO!YLE&!zw))m z>%-TRuPgG3#?;0(fjHK%QLyc?xwCn*ZC6`X$5xw}=nYg2+QbgVSjAscGgFe$>QUUQ z_?POJ$CQs0AIK@Gv1(LlAHKy_{i3$%_xk-pw;JQEb(Yin%J!9&QI`?3jH1lIhRH^KS8R8k zkAp-#T`YaQNxR9mNwSIg1a{hTI&ji^x_Je6rFylGmWNJ(zJE#yp{nUUo748pdr;5{!%AI^&+fq&r9RdiYgo}ieWZ#R0NUSKCFoId?c1Ei?SgEVE z=uQF8aRa-<;Gz7X%bdd;LR~%02=*^*QmU6!dosjwW6}c(sd8Kj<V)<5X?K+y^S#kVujw12M_rGQ9}AH=@wt+GtS(*7RN%>M zP@;XEti$6rwreaED>1s1^HzDjz$1J$Jo;%x5@M17ttunqbMYj}B=qztLGQXWjSNL0 z*WQz%{Krw@6XErVT#3`)jxxUr@N2EAxGbmjH>NoquM2*2Q+uVhuF9-?&^Dq&sqFO0 zbTeo8^PcABY|HH1R~hg5wtKc6x7w!oC+l_B+FRC-=IE2uEi0{PA3+TFs(&t7sBer+yWMVgE3ClcI+-<8?D z<$h+n*Ty?RJ{~)Nc#?Ed_Ol*|?=xRK|Na7Q3yE8E{kvxR;*y#Vx%{Qgts!GL6Hcw~ ze+=%}>`|Uwp6WCQwl8}Y95U^d5C07IobePoC)_jIzy4td^YdIh&N?LD%iiy{iavQ@C9J!Lt4A_jdpz>pMD%K$ZWy!!8J7uad*6BnbE%#{ zyNdVamFo4jP%?yf-D|ygz3rRTw}RnwZ%SXMJGCR5qvnhzE?+E)^eq-?R@bL8Lwx47dKo@26fiGn=xQtJhH3NGA9(=e+vjv~ zt8DT!=Vfh2ZBDJ!_DIu}$A!nH$364Gt4sBciU2*G_BHMxE^BUA8x=dWTUBA(tNV}l zcK>g`?%nSfNOOvh3Xq_m5&Z5Ns}6NQAZsGf_8}2bi3t(Wwkim!2O1$bU;ogtU_glp z+RH9@_jXnMOG)1SmEgQEDEARm#*^;VCqQdVw@}e=){v9sGqST`GBCC?G+~0-*aPw- z2qXaG13ucAI2%A=HrBRId@wmpW@a}xHzqfBCObznW>#KaUS<|HW;QlP;0#75 zcUxxz7^AHd<)54UdmjlCCnHA-duIzfTj;}m4GisEoCPT;9v<|cpFiU?fm!_bNw!Y^ zObeJG^TU6bS(#Xv|8sBPQh|qW`4lZ+Ce|7f7B(ifPQWvSxH-86exLt;`_F%$_}7(h z{(B`G_y1h^*MI)GQh@nk0)I{DPqco23xrGPu>kXbLND}Kc`aNH1QG$sNQkPy;C9oI zy;MHW_AaPkzuahbQ}JM?2=#jec{*5|`-FcB*`sVjwF8xc4!1?ON;ywQsRN#FOfptC z|6E>LjPUt_K+QMD>K*Fu#%?vM?w5?718L9id7ItW1owx6Ypo~Qt~X+H#VFyhp??m4 zMQX(sn1hVGJcbFPwI>J%jJeoUvqc3cfPWp~AW1draynm?>N(|_~ zhvLLB=|8vr=K&xZ5hb!klK!puzfOw*Zn*!SLHwT^{x^U?F#k^sv7!F|XW9I_t^WVq zDX?G>SJyf-HbW*VMMOl3cUiKyGXLy!F}TkkI>=B~&fCyXQIGq!YUIgf{c?nY_%r2b z9yX{QPJe~Sk*i>`FbXVH#P*!)QG0;}d;1MU|3c1(mKFW?684)zbi@&~HS0x{hWddQ z=htt^L`ZO{RPzgjr1|2${>}`(6qSyvFMW$Kw#DFuC}R>5sH~<+W9#QVUPTe}Qk=|Q zqj~q^NhpyW)q~(3V&G?nf{$sE&gUZVfz^r99|Vm_NqNp`HI=|+Gu!{uZ9&d}4CIZ= zplW;}S9wA;C;BiSACV5Qhj8KJ5)pVwF(?Iv*vt1!Wp8ie6@=bUx#(wS%K$UuxK1yl z{x=65Q256^d-ZaAs>}t2c*g^aqoxigtFS(I5$V5M6BY~-ID?#VU>`h%3-{2AHRb&~ zM^Y_512Up6{GhdrAENYsjt+H1+AVL%)YX4q=bt#e2P;l^qA=7v`*#4pL!*b4Re1i? zB1!yV4x;jY^j?VW$TjW{6O!}GnXhOLN&HXh1|z`}pCE}dU%3&{ZrwKfYViM0e(sM4 zNqT35CjS{oMDTDiF{(IxivHV8dnAB9dX>F&-2qJFz^LH{W`knBN z>lvO@?Cj&jzxYuQIsE(m$_42a{#jSPI6Sa}EZKBE)xFkpU2iH%%5Hk=7-k<8^RYY` zcms=4*%Y<_CrE5%Lc$XnSy_&P%RN!}#k-5;=)tYY5|g`|OU=sjjnQrs6v!UC=}^pk ztLLl1Bu1B}lM`nEwp`uO6=FoPu(Aq-Mm!=;|HQK)6oly97e%s~?lzAF+erUjtXh)i zdA>K>ebcogN@wiS;;2OVa-}gnRsfsmFhvJ zn)YJ#3MOO>;+S-Px7qmMkh!}dF@Y#T&X@0RqkV70>ui5oDs-ctgR?S&(FiEazNN*k z4!++mpi~gP{p59jd){a|(d1%9Amjy$D&TF@?TDv>=mQG^p|o2==lA>ae}^K%fl0!r za&^AX%-nX7gS%s3U~m=$?1@o$5_q4Zl`m}GSI#Ls4mlmoZLmW_UiYIsjB!zEB!Tt= zM7xjOgz(?Y`}$I?ZY^`((a1*$YePLS7e@JM*n`RO9>oR*N0}n*Ef- z>qmpk)7Mhbq+esB_%A6BX00k@G&NJbt~Lv>2?(B}6LBRxSN_Ik&J6y&%m+h%d4ZHZL{Yy$ee}WzX-Cja&TL$5q zgTMqvttsMx!zll!NcJ%7T zuu6+ud>u+*|EzQ{hx3Lj;-W`Fw}iYUWK9STHkbb9@@O@kq>fBnuik1}zPxFRPB4XF zNs|K`Obw)l&WR7!sDF0O zY9SjnreDX%xrYUgBQQGs&3>lvdMu~sv-Uyg0z7~*Nd5Zt>l2Oda&P1nioZ;^+XAE` zK7l6F>$PpuCiU$n#1i~bX{ZL6<)e^>N8IioQZ|AJZ79?A05@Wg@NJ+Z7ARy+k+bDW zMJJuldnzzHXh^+X=;+48v`?f{%~LH=^MH)h+bs~2lRoNvR~h{>k#6%9*0(@5$ocJv zIOZ4Nl|GJpR`Hw)?&MHeK~S|{8^()rK?disbz7mJLHQ>gaij2fd?Vttqynd3-W(6R z$k#9UH0$So*e-9D-#3zZ30rm0IsEncw3q{O4^AvnugEwnb=w^KY{FY^Zd6FaweD0GMvcprUZ15nufqxh z<6Nq;Hs)mXe{!J^-lx;>xoj;~Bbe)0p;480m{f>%J(Fv^EF&9_6=8u?dZ{9cJIx^d z39I5WP_~D{HfmY)$(UY)y{dd2-5TDraPr{8S*I6yrWUbt6CzzWNQd6<2IwhY8F#wI z)+dFP&N9Ew4(jhtf2=E(Ud<&c?E3-x)Kh|sTpp^8axsAxTbwVkn4MX*WC-nU3gsxF$l+*A<1srf)+_1K z)KsepTVu$d$ZXJFfyMPF>q*!)$>vER#NLswOrC^5m@ zM)S>zKgIw~tFH0qwzTVX%kM$FNJy*i-sPEv%c^fC(fZqP3K;mcHj5cwqs*OsG@^Kx zBe_*v03>F}1w!I9iAlF>+7ovz!RO{0y2gcc_sN!0Hml@PZ<-a}dDTefS?OraX3*V( zKbHm*h9)RYi#rSdltUzSnb<7#m<5s2-rtu)zLyT%Sw}MdENQj5w!#QUvt@Ra23$?5 zkWL|(a|sPL33*&mxt_1a$~8%Ni6LflbFGJE4wC3cZDIs^u#c*ojFLBxTTTC1E5-fR zb4Ml}R#k68qUVm9tG8>fV=2QL!e0RES6ak7&*I+=GlK}#CU3zRlW3w>LK(HH4dD;x zP!I5l#;z~HoIyOicd12@3<~5>U5CoPq8rr~{6?KXr2YxzSFXH-aWY+nKlU&r7xr^> zYz;1CnrI#J_(^UM?NAe0NtC*ZA+ZA1oq(}t`wMi2QY8P#&d#D0)PVW45Od#OTCo=@ zv7)=y0mKLayDvv_@1kj$+n5wq;VJ}rc($VbMdY5%L>JlQ*P3iQa8@eikOh$Ll9g-d zgZ$tSXZ?-_i$syP0{juj@Y%0vk^6{B9AlYh^d>vFXgmCnSLH#i;cMv@A?C}-}ZrL4M z*RtN5Rw&ofVI5)5b20BlgE~Tiaj=y?vLJULGI7=Y0Z;pgcwQ=@gg(TO5!s^pt~|P? z<)9~9g*A57Q&Q-DJn2`WF2!jgOfP>HNjwx42@c=url#4Z5}q~sh-DZw?}#7d=~5dB zhq?7gTo-ayD5YC>xbLW#Nf%Dg6@-zY8i?m2IM9UyXW!Xj@mWYqI9Xs6c_Ug$cy7KE zk@a53at=x5;HLd5zAS3_TD!2OF=HQC33x!()6?%{{Ijn?)S$!A3svHP_ z9olLPr^`2+2`mGuDG0WJi9H9{W8&-Rm2OT38tp!J%XDS>z_AUQ0ekEgp*AuzUk?}B zuAhN@;E@41nl<>$aDlH-ME8<40YM3)n-ezX;Hxz!bcal1&*@T`^sZCFofE`YmLZ)i zz;ZC4wt1M>9fYpa|J8MUJxgQl zWS}-Oo&)IdQ=5SL^w}z5T33Ds@hau zq5ZmF3JW2yvH6OpAY_l;BS1~wJr{j^tI`iaTQxe(#8tJqzPMi&w)VD{)X_43(&eC5 zT&L9?zEh;CI~7BB?O+Sg3v+k_My=W*ArA@f+|hrE(<}&LHDkETWU(rnrChq$%3AuX z!|l?8LgqP7@~AofXWxA`P%>;2RPn{rmo8tlv@egP;`8XMk_FX5pA=>VuL_ZGRe8}^ z4{_GPeP&DDXgR4?5SaJg!iTC1=fuRqjyGNt6f7#rel6uzAFL9xO zGRpm8?oJ9}qQib)cXLK5vj47*<(Q|Bc#$6k7UOr7n)MG|5iy4xoG}+@KJS{_Lm4dl z2G;8=sSJkTqhUZ?17(Uegs_j%BgzD=0fR<81`{z2AwSMZKWjbLnhu3BFl#?QLgDfM zl;UD39qo7}VeKy)jCd7J?M3hPCsr23Q^0fb@cvSM8CM{H4ABw2x%psIuYvJ>;9 zp$J646^po0bk1szEA>xJ`)A!`P>U$-TjUHy|3#zx5WN7^WWKNC4e@X0_%H2(rGg|| z3&Plh{~~~J*axg|@(HK^-Z)zfwC()Qc)i5^GCUUSO`rd>ME{7fi<}P~9rlh3ArKS>Q)t=kbj;;fwKWS%Yhxkz@ zuTwCZ6J$xg5|BDD&qz(LA7TZS01tiOR^W5nW0=-)OZRcvnNhMI!mG2IX0iYZ!YI70 zqdqd<2A!L;-MM`65R9=3Jz@Wbf=22}y9J@m`PSx>y`NecUPm%tQGea7zSm3AZS|0; zxBY1hTwKn+NPrEdfKQ_(l1TsZ@nO6oh1kigM!^qaLWb|1d*jgn{WAdpZJ(P%DaO6H zxVROv`-_n2Q3(l&e$V|@8lbv<52z7u8tk(Lj`}ItJkP9)lyYCR4K6gfluQ(>zWONl zfx16_Ewv;3DgDaY2fHMi449a0>!}*A^F~Ypo$5@!^#9zzHt7Y}`ae%fVZ`*SC0;q~3dOm-)s5+leRSsW@Rn25 zy{I3zCEzLmirUld>G$N~!5bdLLS7o{$A^7n+x~rm=Ra}<2O#MOY`ILd2)dWI*XP?D zuuKk%xbn;z=Yto^gaTm=K>1`0NCSK~##bkse8K|HI~(#K@&tH^^mffE>FjW zSy)(9KUB(hOOxKqk=!R-Etilp1Z0c}G1B?NLFRVteKJ806&C#tedx1ilJ7QvcnqlP zd9P|jc#{PpBs?O&1x^AZ;T$wkW}Ywj>bdUBkYfs6WIgB^q~0e=jCJJw5HL z(ov@#2>0Mjm63}_0>9}HKI1(3$b&LLz+oOE0?8Fv3A_@kDK=Dqn&%It zRxH(E{n=DmS@}*AC7KIyzR_v@q|q$H{RPAdQ`~%LqDVO(*c8>C=eCzu+Z8U!Xac+c z${WrmgGo6;M_Q#9~-vmNn2>*VIa$lSgOKSD9q|% z-{VDM0acTk?S$b^a_zuDgxW4WcdeU6kCK#$H@xiR!ULwpertsVAAgFD#@j(x}Q2BsgNDz(K(3nO!zPI}PILTLdv{*lyaB z9xnGP3UyhR215uY9x;cyB_9@N3j6B%+@7l68h3oEa6euPz-u`Gv$G*Uw|hT-)&9ykkS!(;b2`$ zs=YzdJtbP`5mLl&=4 zg=r9Rr7^8JtiTs<1_(A7$DN28+Q`v-T@H>~uW>e;Tz8ARqaYy|rpb_ZouD3mwYW|P zc6~80cE;-;j)ROx*Zb|;iqB;G8DDm5BM9*~c8A-yH`bMAT)}s+&;YhA3kKfRgGH0J7s= zBSurH+U#W!>2gd@HjmKoG=j}8UIcZf9iQ=EK_XbV;j>@hXJs!mm#DrS@Iva{e}!iKi~z%7`V&ZVdeGn=yE5#jM9*;$w%}XjKpU zvRs~!J~D0lAC(fMJW+T&yt>Q9Xm%vrx515QYQc+sopA&gJW0_qJuqzl&Uf`_3WBA_ z*rlh(YAHk9&JSWzllO4aLnl{c1WTk4tosd(;>i+a`Irb;i>8imuzS4kh$tju!P%5$ z*;Y{JD?+7wPwiURa{0G6AG*nTtK zH-~*LX|;nA0$6N__QFu>&=>HX5JODhgInVWhN1}*Y7UZzx2!>^b8Q^vPk+Y|EF#3 zM=qjdCw-9q*G>Hp;S+%3$j_CyMDBm+VK4xf*{xq-Ld9i>VKW(kAx=k;@UKMi@7bqLKP2c( zucI)45%CD>#RQtq0X;CrXu-2&=Z%rhT?VudKy$+i*Vb%N3Xh70=GFb(?JA%aH>urT zoyOzoc`3bCR$gt|E|1U4qw*HuGX$M5+1QTjhXH-KTQ^Pc;Y1#E0=#PLr&+FwKxHboeI4*#k={At8gYlu|3@ z&3kbVkVOdOzWeKidqf0$BR~@8`fznSKwpu7%c!|=ceyTn|J-Kw(`aDLr%xQw=ogMp z`bn^9;o;HRpTlo3#QlkE4WJ(1%#ntY| zri`hqpbo2*{#Z7!-;B$Q~OtHLwH4>wST2i3aPYI@2LnB!}Ju2~5OJAWJSUzAAc zCo(+AjTVXnxT6ItpZN%M_ibMzK%h3SPIu?jG022U-)_y;TCD=HXd;DN05F*d0RE=) z$MXJrfUivVjkGx|_o5({u!5KLSzrs~GaooCD1a7dNee*JJVf3u1KGQ#op??wTkO$K zsne~=_=lzxpgp^gH1unSj>JZa^4)1Jlp$8|9~{VPL@K*rq&m4LuNwEy-z3AT?BouHfb2Q zV*9R6w_Wg2jynB}hLTzNh#%RAcmfMV@bcF?=9TqK-y~kAwZ*tBPT1yqMlI@Qw|&== z$ZuC)%g~aO5pRGE)SBsvRwDU(11*xm!Ai)T>#e`%d?xKO(B}~X7%2gZzTe5_xKxP2 zZ-U*jv{d%HqqM)!u2&#seFtz=6CgewF)<4g*k za%chqOTEz0@$vC|pq*6haca36O9qg(sKkX&7V)K8_1|_;63Pes3qt@-H}IsQ+X6xd z@D600#{nL^!7)&hmZ9Vr)b4RG{%j-*G>Eh_-mVnbr>5+*3x`xl2t=|OpAk(3erCmr z&_2{}tMg`a4@&_GMiE)*{M}yK{qh2*%5WftTpaOm8`24`72Og1RRhetm}Xi`h4Lc_ zIrqUwaSU2FLAI@6(ll2Fq~)-e$fKjueo0KQ(*1h3em6(BVjJPI z<#5WVtqWjEX&6E9jozjFC=KF%OWb=ShMIp;T{{g3liToXWM}TX$^?t?k6$*&3tUPC z4ZmagVu(f@5Wy~tjEwSuX3|)(D!m}M!&p^n)aJ> z&!o|T;gHs9>dm{YpRjE#t>^;AjRhPUd03>AQf>TdoQMy2#Tjd5{qe^?&;W%Krd-4? z4p5b=JmXOd@;7MpD0L1z9Wn^j3sEPXCO0K9V1a}}4nq~B%rU5I)=Z_h@%J;dcxmaW zse3c>jna2%CXfcW-Pe;atd5r7K6S}}{X!w(3$kK$TU?G7P6C+nHkamLZ4wUJ+`&}t zZL$KK_%+FNQGFdwAU7cjBBg(2QkkYHnV=&F{#-BD9~t8!2Gla&TUkmeuy|(*jusVM zN(l))Pr587wz{n97Fygls*Cvx-Jtyskok`Z;XkO^sQ>`-#dR{{L&5X!0d@p{ zLUg{5)({R?iZU{UCgMqAVjPH+c%AAlY(v5Yk#bqQ(ONC8MD5zQ13ZfZw$g z=r>YK4<<3`&^fIQec_BeHLf!J{NOW)pDah}M1J1ev?btA-Wdkx<>g8LKRF%7ZvdwQIOy_Ur$d%_-hL7G|;bd-PLUT6;6NBRup2f4=533+ib7{eO{m``)yX0 z-~MQ0G?xv4Rc|@KqypqT#<;}9XUy$4)#BuafDGdW3V5NN0J}2p z^gddVA^BJX7+F$;ecN#3h`6j{f`Smk!o%6VYoA1oWB{B%8mJV?CE1SvxGSgydv9ci ztP~Ywj2S$?lv^*(fNb|~H}AK_KeW;5R0^{s%Zi93xWuBNA4i$;{)ND)`AcfK)c#2B z`NHm40MDP54>(xs15JKs-opFC<-S#bR2>05^1(11niT-+t{%C{ec+mWpX!l(W?1=F z6cb5W&-*kHcd2|9t_rg%s*XHw9dK_XJ}5f?Kcoiy6i3~d!W(QXBBB?VVqq+hYe0I+ zx121FQe7892_gpecg(gU*Y7$!ARZLN9K_$!4DkVz`7d1nrVrx|Ke(|11+rZWQclZ+ zGcEwA)qnyvxApq^e1Ccq(C~^Mv9)}|rxHne<&n64ZCK3BZ|}8IZeXErIRuzM+BVE3)?XbVY@`s05&Z=m7o<$_IM{ooeyMpsZkJ z;F(y*av0o2mcpWr+a$)2s))`~Vuey}u)xhhcfgr`)>yNfowuMyj-Ea(Ss>a(qi7(~ z75+UX;CY1*3`G8cOFzVb5D+3+5S73eu!3k|I4k((dyU!ldtM~C@Z^&WLC>uQ2Ush4 ze=J7EA|RQdbiHt7Pe6%g3lc`cWI@B$HyvZjz+d4`FY%zr1G|&~b>KIm`=w34T=F(j za%o`n^_iC6tMlhy;G-V-HPRu&6I31c#$X^I2DRwtFp3#Mj+}nFOn<3pzbk$uc#*CB zX%v4pDr|5H4lCm$F|T8f2|qw584~H$ako1_fylDbfUHo3d$WOuhNkO%s=C{V90+8* z)xw%0gasMs1W?L^Xhzqx{?;&85Epeq`aEYU4P5=f3g-Y1aBku1q3IHbCM=oshBE@I zwE{Qme_SSgJlugXAqSjDOFKhHAHJyyvTAe^gL*270vqZG2Vj7*m#0$ny83|>bco9G zm$RF8xo9UMkg9e2Au2#Cn;<(tF*CXkxb=S1csm8aMAp8(E*$Esz8e}DS=;yXLko0q zlvIGRVI}U>r}g$%@0rHhygeCrSRL@-7YHp)%2)YOf(ZT77Qoq49(C`3=Q-#GSY$`D z^#tN|z@_kkORmq)$oFJply8q%tRd>CRGdRxg(3oxbsf@r@KQXeiA{T3X0R*+U%SI9 z^1?gRu;-fjP4x-|E2u`>HpNj9EdbUd3%|3 z$UmqFALN%iO(=$w&8~rhbws6=xs=se}i49Whku2LAbU)UrXX+_B#6ES@d65D4@Cs5 z2mxqmRTrAtokMT;EUC3ojGyQuwFcHz0}!GRzuVr#;Z@W$PaWQRCxMrCEdm1FkPB?- zE#3+0bjwXOV;kulzI7){zle~AIN6}HTB(K-*}5+kWDBuNv(7Tb`=ozValPa0Pwo38 z&TrBw(u9DV@Am8BrX)aL+^7X^^V`a|!jfSO=wVk{$mmlZMxO~_JF!T=@ZuH73rBT> z_LJdI${kdrIEC%3*QYQh$ZUE#P%A|0S}os_GSpfQWdcSUsWxOLz%GPPzpvr+he&Xv zh-@GQG#1kcoVdGxT$1b?Og@z=Dm}dC*)Jw`0_1ons}Q5xR#oJ+SMZ%L{8&#rr*f?^ z|0W#$fZB-J$Yd7yKZGL^ARLvav~&OC%5i*f<&+P8*Z(hxf%@xH0^G=2aNz6@!2kLE zzq#`tMFBeV;L6d8t`__cF#0e=f7eKP-=8cKQx}?(pLYbkuiQDz#~2JX>0ytRsBs7 z^#CGx&gqc!H#-%9Cw=Il8DtGb{lz(f9@>N3b-L%x-%JvO0!s$U#Q)a;#~}Of>{vfg z2>@4^q7&wMBaaS`65RQO6(-+Z#)zO>W zkCkb0Kj_l{gOqt_9sx$nVRfHJa-W>mb=n9u-F0jpaW?GmGxBj4`2Zu0B$f3%r0ZKKckhD$^tNGEJqSm2M+vA`0hd+ z5Jafle!8e*9BzIk>}qZ^=tgQTbgO63ZU(vwjhi1o}+g+$Mog9 zRp9Y5rlub`tY;K8>#U1j2?G?I0mzMua^;HI0USX0#B!oA`_XBp@7?nQ&Ay(V4LETC z3{E%?G?qQkh-35sr4;cO?q!EoJK$w)e$P)&|ElfwOzSrr97iy&1j^)xMjHpvAzKf* zk9dCv$UYMRq`aZ-3z>;|+jrxB(XQ91!fX?`Xofmx3<w zI^=`}P3(vb4Grl3WlQoOb)lL-ospeT7AN~Ukos5-I-rlP4@MT;*VAWfqC5MN7`0AV zVP{0#w$|%`ooM9_(<~iD+KtsdU4CavVL_~)Py>+!ygP6L01d**6n`koHa0f)O5p6l zXSN3;`XAfLf+{2?K*w>;dz2Sh>P zfToJt^2L;mHcFI=h`ozsom_f})6E1B3X_0J#i9y5x|Ng6De|y~4CufYs}vbxY`dXR zmy)vx&G^!DK*eJitma%YD!6ST7 zgOxsLUzqw>GlhbT@~jHo70|cF1)v8?!$2wYI^_SV>#d`rYTK}HO1e{|kw#jYp^;_) zr4^)ax?zX`Bm_a}l#=e0mJWvoNm07Hb70`z=<|H*e!h3TYq9oUo6X)c`-<~8e#Z%R zsyC66A~4DJJrwS@U(HnhE@M(GNG=X&A`&x45dnZ{(fpldW3H!AuCJSlz|^Lvm1ye0 zD$Ra+)M(n3X}0@A5u{6iLS5x1yYM*X%djqiC_2)? z6Ep;HuZ$@qfhX0jqktd1H=9>b@T)Cq86v%g9*kZr0;VRSPSFNplmr! zX^D6qF79Oo`4z}ZL-H-UWvRD9r!TVIl@9SNQ#?qQpxJS5lS=wT$UL`d>8Te?0`p0M_MDh&@&WL~K0?v=m=qa|&C7$FEej|m@%Ua{^k{a|!NQrD zOHV>>0|i*9Rz(2#umkj8hNuV8D0&%TYWwGPd-s<0?RiBP2|m%D)B6}gOcfZ!X_AI< zCS)naXH`Vv7p8~HCPtnnx_s>v;fa95uje#|aeBs$w99Nt*66I$Eki;l@`&_&0fy%< zw$kikgh#T=|4HVX(8Y9tHK#ql_Qp`0q%;K;(G7e}3iiylFLj1dBex7qgxn^OVA>qH z_u&$2nb@VFX5W>WzkLXSRKX+b{)Rx<(2x~>IMxLHboIoC(O@8LJkdLB{H{g1YJ)7X zb7Zl}ycNrXR=v6-GBOaXH?Je6$mdj{xG>TcfIY4oUwA&>bG7<-$C~U+$PJajKe~w4U!1_)nZAJ8VegDsKNgc&>hc&xFmOvg%_K z#mnqoE$;}+%#qoDrX%jy5x(kO0G2zD&ExpkavrHN{!-EoG{$OjuKyyV*s?$xD%{(i zO3TULqKMx63=(BfoRwYfjMoOR}j9x zdu+^((|?AV9iomi&}0(>&rjdZP>;xkj zE1hEBP1l4n#YmxS2*~h2?;w0Soevw-behV)ADJc^b#DX_Uy6t-P^L2n-Yoi&m*G-N z@l3nTvApX7uE&E5GFJVwGyQ_~_}C0h)!n_8iG?K&A1mb9I{>i3mc-zNjVkuZns&FU z(4PR(gfUlO>LycQe%VpiiSAX^s!o}Hb^3=0XC5vt_3?>`a~wN$b8oShf9@1I=nkLG z@oZ{qufMh}v9PjGN@3&SlF)IUHp6Fbt-tdi$rehPi*S^^FLIbNA||3_XErm-lehnP zmpM>6PROYn-9p3zOqHZx%Pfnv^J|OxIe9W!0Zcq_6cr6*{9x(e_}Kj(TAK0s_?t;n zAH|fClG0DoP(Q-)wbQiodnEo9O4(*$zXm5GBTHN*$fGi#U}JC7AIXy90Tzr29$em` zx2UKDU+W#;@oy>^KV1S}617Rk#l4(F#FzEldNZ#~(epl|HvDl>ftDLlJDu~xPCCV< z6O--uU4YM0J{<3t@uYA4PJ4JC+j+*T*DB=Ebu^>-Xis;JqbLr*EvvrVKoTclCiQuf zMfXc4LQ=FNFR}ndzN+3u%{}o7b+8s4>6?A8Pr#QN%-u;ReY-*(A}BA2=AU;v@993n?R0?1G!WhRzC~-Ms)g5nyB>%hOMuG(>-9z z9x6hErCbRw!sSA%U{CFwC2tE$^vI$+g zxx3K)&=^g>_oIDaz9V4aYz7Vhc14GQ_faffDdg)pQ#nN0*JJi{`eT z=TFgTgP%xP6P|JGsSG4>rB$XFfRjdB{1iLVF15_YMU}_m=@SESqVteW-!#Bmm@tp3 z%5ZfYQxdcm6`5a&L~**YEW}RxNHCm#d^Uey&Q#E=YIWi5!ENnGWU8fIqHnWpSen(- zn=tGh=gYLDi1snCLARfJaChDZuR*!vB~Xxo6vn%+m!j!=gyltAwlgs!`Hsu`B1vW> z=1l!RX9yqUe*K`l!w!xkH=kXuhiFMTNS3ZMpfpBz)$mU(sWWj`)JA>vN~|L~5^<^@ z7Dq!|erroOO(i_7U|k9;E|iR2)^b%xh_mm#dAH%x&iGcor8r?$_)x@gUTFJD10|Cw z#v1ATN3P;J5DJ`#&%l1k+cpU>BODKbw#r91B$Vk?e_?$SzzO&psWRZ z$eeYB;_!%tp%&dJ(m~har`{edM@L3ZEcl!u_drc?gYE!#T1;v!?RPSch#%lR*8KA$ zr;Bv^haC`~W2$U9iO4HS)S27H7^1+mJUxRZgkw#8z={i9*JgCR99#YBxp8K5Gf07m z$yGbAjohF_f#1lU3&TMScORKbN3%KQ3{Mee^`Bm%(8AUB&-H@QR3SmD^-u7NYWOW? z-+7DCRBT4#-d@vIEp!(Z&cZf(n)i3yx>uQ&uu!}s;6O29(Cl7p%#dI8h#Sz*g&gMq zQtiQjw)YgR$P)LenDf8c_o)k|W~KJ5TEUg~ZHai~X*HP4lMIv!V&cqzC7J|S$mR3j zd61BvMm+Qam~91Xka%CwTa7+N!!W)HdV-Fo{|@DvzWw$mpcirk09=!Q9GnTS=N2I5 zc-Yz5uMaSA=X@^qise%Mw3Vf}dq^&|B6fo1*YjrM!^AzG3>BiJd7~QYhbMIGIN3mIyH?5*%(fQ6kY#-;4_bV`gqh_EE zS;N)Qr%GXGjU#KlmpCrJESB4!4Q+Ov#XbylNSbtJ4(%Xc=aAvf2A{1A$9p@T)-!Fc z7Ipte{jgaKb;p4zDRTBnO6u;sjLswny8EJr49o7xV^= z4%@O;{!x zJD1KV$w(>>B3p(q)8>!U64mtDO=2R$7LKXMSH)nfbC)JEgKbS?!ro9JNG6(uI{jP- zD}9S80Ah`2%VBKKHGS$ zn23Rolmcrb;)j!#0mr=*HDcs4Dnv0m>Kniad5FuR9KwsV za%;n&fDhm72)hJW? zz~*Im&|{H+lYZ9b(ay(eW7d!r*HO^r76LH-jd>!sH4G;o?IVNTMj0dqo#jm!Cb2dj z;;ukxT;2*Vpo<~D`~kqdg%b?>;Y3f-q>A1b$~0!V9Intvp#;GZK$;US`QjHA2}|Sf zgfSMK6X`kBePxop7mOuB7PMTEsC{WXY*@FKocPQ@MT1(3`#udc=s(n4?XXMkeLNd5 z0QH(@7?l*1)h#|m^}DMEc@D8?Q4>#X@%;7bw_tP@S5+{JF_2e(DNi)1ME;SY(OI{b>*O*9Ms@V6 zV`?)2zkm)T5&n98Mk7=F^J1RpIN4bZAA~a-S0M?kTG7Uz&_7~=*4{WFc+?(-Qo0nWQ3}XwBRlFuZv-jA$1H2~A z``b;aI_Hp|nScrQAUPE(JQJMO5xxNE?0=AF8ePnr;5(%r3qTC_M>Y$A#8II8&ZM%{ zXlD7Tg0Bz&y77d`|A1CE5;p+oPq<@dhUoO28(x3VKKRtlfs;R~P|Z1xDmy`+Zx>#V@-DM%u2RkHz^miv6jVpYOV|PWD8W0{^#$XS4V~`+DPDlKnB)0}XqZZ$3<->GUEH2c zfW`38DefEhp&op- zUR^&Ah>qpj5l3QlJulITD?(rTU2h*tV;k6hHq#6L+GMke-fGh1N@nNzXhB0sg!A6# z*n2ida&vtO+U|ltH?Y2zthM?m_SQKzduOH|igB$vwc8XRxt?rlqMlY4V-jF&L2*HN z_UF^NM9r*ESMM|Vhd!yi_7~J4lkBw1LD1x97QQG=ro-3pb*b5j9$SNpwOIA)Zbz3f>>SO9$*L;s!{6(`&Z7nj!WNCweI(RKRZ8)x$z9U1NZ06Y+H zKoIqy1l-igGD2euLEdkG;8+`TIG!I#-t*_F!Q%8|;B*lNGEUve_2vOosb`^u1WIAM z*ydX=yU{MO(XIPVr;VJZF7aCy3V2S_JOSmQMg{9R?#Bmpu@r;n<^k10MaLZj>wX8& z&a5ZPOh4NJ(pfB{j&AI5%Nm!MVJnv6M4=CFgpx-RPK_F`Nb4=%@M!-rV7DLK0I7Wy zAj&KH{dy)x$*_qBQBtIE8tdIM&JG}!;wKHQ@Ju_LVDwA2GE7g2W zR_{EvMy>N_C;VzQ1aE{wT09p0WgV8p0QKa7%UnQX{3I>=4~{XWMn~1j<+Z73VCuExEN-OF;qpYT8qngUO;IJ9}}QAGdN% zf})Tbv_Qh9G0f>2wtq4Ui_eenakbt{IhpL1yj_AK_+insAV%SNzsR9m+vbx#r}&J3 z{TN!k^MrWTD9+gSH@@3MiqUl1ZkCwW*P}NSaQ`Jl@S6y@Ifoz4bgh9KA_{I?f*zHY zE|D$azgKj(KzZE5n=ySGCU%o6(;+u@UxBW(FXkB+gy}QEJx5_c%x*muA)*yame}Zp zcwQ*`fy0%_C9CQA;$dSHkZ=VIl^Ef7N|>+1>2CP|7muz^@kwcB%hgKcua}FtiUb*v zQ*xmWrQvcY;i`6Jt)=}1BPA9+$)cN$(W?c1;R5D_$s@R>=k(7|8K@u}NZA3yf-`GM zJ7piKvF3mdnuzlmlfyF(AP#8pD2VnDf}%|bZtbTAvsH~qNKA~N(})20mHVCTW71Au zyJv=VG7zfIA-w}j0{bUC|PBQ>c)kmsS7^PhVkvLMOKf-}oBmmKI~kJ(aK zpR>`SiiWt0O1`N!-Ua_|Yl-fVGzM+|;GBo(k5LuOobR)SE8IKYNw_HuupQ(2ZvBAe zseikuUoGJ#iX|!uP%XZZ)DS8&sWhLaVh8(nzxZU?1aE?s}W0z5ogG0&44_m_R==U*HkS&I- zW8;d~*IhU_W%e{CK-Wvr!YFj-B9r=JYOq*YfHOz?>m#{W|N0J`A&m@CK*Nq4IeU6^ z2G^=vQ^&5kaC@%I=^Q#Ls~A6G=8$`Y z9fdjvTayRj!``HRz0jX9d{l7WI1A{x`<~B9P1ror3q!9k^(qe}68XXi|3 zHfA-_eHz_Fj5*xZK>`+a#?O|zhtIU{fxW3uFAJf-cz}V^Ny{!6Ia<1m-XDhFpc7OR z{M6Fet#|NnSuBnrhpbtvrR5|S^+=*yV^+!(sfRSzS2Qa=DY18a8O2wlVsKNg!NUx z`?^i0u~e;4gtOxXUJh1*a%rcx;oItXixd2nv$92d(eAMl;|NVU z(E!@O+LOjYz>G3pbq`-pD4@C zw%e0O-f$=13D341mEYr+12$aS9ksA_4y~?^_j0L$Y>%4%BdB7FBs%q#AM|*emBTY2 z8QQU&vRTgYu_&!MD~ZRbWVc1VJktaA#!Gc#qkfDAcBatOZnFxf<~w8gP7A}aYcv6H z@3k`5W)T62;eFk2?RWY5)?Euecq6M6maz*4;n{**4S$_-d$g{EzTx*pofNEhfik3K zRPkWM@gOPCEyNpBuQWy8?PFtTA$g_;1X7JxjXC!Jb@TLyy5)Dr7hUpAmqWvEK#96w1)xR2FwiD|z?5l5| z4rQnR+??W%UNa`0&^k-=ZIyG7=HuVF{$+SB8^R^}SKkg?4#U12$>}KK)5W@Sq(22D zir-TZ%eBZFmu{cb>vLg86T4OQ00( zR=RHWSSINi8xdHR@N-UijB$Vwi}!tWVHC|2e+nUrekUq@f!A#XbB{4DM@?;$eaV}d)$bzd<_%Tqr3p_W-!V}DG2j4hM(yCxTT`nm251{&dDdQK9dx zaw2TB8Y1(o;)7b=585Q*s^rnJ`hu5Xe5cuC*Y-~Vb)E;1ns4Gf83uwjP#Jpp`jN}#jq(I<3N8$U z;Zk|f6s~mJ`@X`z-2`1xgP(ZK+3UAjY^3K__V z(Cq=Dct^-YSP%I5+%}X!G@~qG_{b22x){ay?Now{sLRzPv#MhM8hvFS57iO}2~f^o z8iO=S+5*D2+5W|_(cW7Sc=~oi-rS2WL_$J)?fY|}dzjc7r&@V^9`2>Ji2vTl|2zO2 z%5rG)XNvy`y&z$ciUJNJ;~|Rf|IZr$P?t96TL^IVKQQdy)w(pvX; zYJ*C#a#-R_Tu%)m;R$C<1}<--+=~UJ&2m&o3v7(P34Q5u(w-P!JNjYn$|7lOW)`75 z6+xD7o5R`2h&-&_|kpf^!~jgANv^l!sajhT6P z4+1waAuCRA{cXRlbi7`FrcukPK2qh7r6$SNzL&wVxPPY<#d4U)d}FQr!m1gRA>|-{ z@cWyd?M(41*u&M30ckiFu&i$k~XV;{(;TYPu>L(evF*a5q9Yw?{Hh#8wT`l|QgP5;wRE7w{REe(E z7>IL^&o(a>nA1o%GH;;gPKINPpd-nqV zI~rjSS$UAh61emThIg6)X9%6ir}j%d{Q}x7+}vOp zCk6cicN^u=K26%2366rcnsd?yWqJ$DrPHr|{lvw(<;`cUZSAe|knyQa`0o0QiGLCx zG1_TG^F->I(6U=kO14qlfxVA@d+jmV6c_Vvw|bp>p~-pz@N5V`PY)V7wQz4v-X{4T z(lH_6i}bK)ns@>!h{>;pL$)lx+gR?y{^h5W1pYmPVet#en1Wlh*OhwtHm4i#xoNJn zbCO^=41yhg3<9XM&)FU`YZP6>roejSs5@oD+yz0?I$guA1Tpc*zzqp2Hu^INJkV42 zXSe1eSZ8+TVw<(jc4iuO^(PPv%zA4t=p}|)Z3>QyVe2;;bc5>2xXGAg7yCHfi<-Ak z|J{tsyu1j*cgu%aF5?P90NTXJ`1HK9vOpttK&Nyd5mYgbHB)I+I)5ui>!-9alFGF? zWtjHi!-o?@&^1Q^=*0_!Z~A1p9=Py)I-sAunBzcL?vv7rD;Fc9#9mHJI=1CNk^WkD zT-jY8h2D97taK5Pk{-CJo^9FhylzH051wwsrSa)RD&_Wrr29&bOXtgP2YMG{UDwfz zdV@dta@SKSj1vlmKbP`m)Nxo?S4$L!_;bj&Vb6C`;9P*&81DPmqJcgMs!T7ic0B;F z>p>->Foq|W8P{olZxwn0K;oP{?P7+&hLkba*xP_50N!*r;=P<2u+#b7ji-$XkV+Ci zIBARpKZ+mSP)}Riw$3C0=+>YOE~Ao81rqOzVxqW|82bAsh|jlm&@{j6YwL@5K}CHn zi@FsF74ywTX@h?iG9c%xLNAB-wO5_jsxi9mS*5XU1s;A^!Q^{tH5m;q~ z7}(Q(-#^l@p6>{ck-QDKJrJL5^C-RO>yE!)2)j=NdR-LDC<=(?Zu|fO=$yLGUP#`V zMYM9y{bifzk@e8DN3-J3VF9s2_LnT}y6jqtzor_eb?S{lnF%ROT3SDTi6(uH%ehB? zIw?^TLfo1GbZnr&*Rs#x#TYeCISK3@pW=^#41tdBI>m-#0P;WC7-9?}2NOeXTP%x< zZHV<4E=7D2KE+1lvJ%706T|Lm;lW_Q!)HQr@~I^r4R3I(#U;xW^4-8~dj08$&$Qk< zlKf&+N)k*sc+}V(Q}1f|TjiyJL8`{3`W@Ru4}4jy)uj0&h|a!fZ%ReSwC1#uhF=3j z!Eej!%qywyF}aGG?4YQ z>P4?z<(fxvy1EpX@5+p-ngv!}5;Rz1!j}>Gj(p|t+MEF7tmPRkc^4wjNb7l1?=W8G z9T`b1LR*w8>+o?ay6#rSLv6Dk8nPfSzlKZY%zDoz$SayfL_K)XG~rmlj7-=;Asw&E zJ;mULaB5LjNqA<15j={(t;4nWcCr6RU^C!lHvf0R+yy z|AvbDK6Mxh|b|$P@ zkP(Y(0cAYVmq6ga+NteTQ8-{|26oM@)oEX!JW6bFQVC z|A?*h!z^b;+TEYQcNTT~`!+LU(ebECm>qUio{|x?pH{Y8tVgW>!f7|af@e{1O;%qK z5iJ-T5Sz$DUhC(`D|fDT^GMyinh`Ld@vNoE>00#<)m387)8{wn`}Y+Ux$6D z0earQnQeE9FZz;oSpy8Oa{Z~Z5)#<%5pUz}a`?3AF`T1od zKL&BDre?RCX>kxd!3yDcH?V{8i}%v<_UFvn_Py_T)bcM$=sIm(1fJwQFrqmw2`D*8 zzJIFAg4qhth%s16B67xrV4A`(s4q*CeeLd;RzYe1H31%F-b>Rs$3dWlu*isNZhF`n zJwBa@#Zwb+9b?MtoRhNv2cAyJ!WY-bNjz@`KGb;f|7UnQzxeX1x@NrYVwm6U6rw!p zy07WlBE;PscUI=x(DP!GhV}qb&U!(UeD%DvJrvLP_QM{aL=S{CEdCfA0p+)NWA=B_ z!5w#^_wJy+mS;a_ELTE=^9l@U@dLI@kAgs;Tjkb>(DT?fRt~%2)t>%%jw@Y|s~*V# zwi)Z>iJxs!hVi#H`Wf+WR_Ab<5&YA~Sdc{N8}d)s8TSU~H+T@A&=1A=>1Avl+yEVN zM-)at5ZHj{(J6NA%>6|Y@+76eUsO!WZp54{)8hP%PL2f@NObz8$NJ{)mrSXD(0oXg zwCO$ift0hfp`hJPtt=;jAJ?~4VG+1faJ&cBM$6ST{>FmkZ(t9E zlK60U8!S8ELh8gv;`gN}ZEi|t$wfO!HVhed##j3k$yifZ;0XBKKxb2AkmWL8aM%bP z8i)gvkCu#v**YQY#~bnT3K?Gs_O1DH)QSJ8Z+PChR_o*`hh8-4@~SCs{8ajFMxy^{ zgsyyPaNw#+kZdX>P);#=N7=(A;66y#xRk?o$>-7Bb)pPOk7D z=2ss^6)D_6P8Wl|fQ@C1Dka+v$VJ<=m@XKuj8b`6W_HR1UZx+yW6Pkh&&&_yDv;y7 zI`M5%v$wQ)Q{GTp^6RBuxncizPnoQ&W^&8Vfk%^6(nrmD<*yCm06FXRxG3`qxOAP{ z!9`sk&i|tPr&e*?XHu%wCgth^`(58+;%ee7=MkUq-%Lw7D2kFAS>u zhiS&%ZU5G|w%xT)e^DZf*8Zy&D3ZQ(1UzTM z5U2s4JLs!k&`8R-m`r96^{lT(;x1r?tIfGRUnB%7HQ{sv?1$2M?L`OO9eNTi@3RID z_`GNY9K{ps?nt=As5MaUlpna~02bi>r7rPz|5WJ*B+{5(?+w+MwGoXamALEIuANDN zscgHY_-{r3=NnZ(a^t?-TdWLi0Rd|Pwu_)3fZzN-iRwW>&=k#u zh2vIh;bg+t=0B=b;` zj3j=N$;S~(GPBVrp#}d;grGJWv3)q(xVYG8J-1zV{%Bt`EeG&i+?AQ~zHq+OKKS_R zcv^$}JWH#tmWP4?nP!5%ipCglaz&Kox@QvrVcr6f=o*AuBN(k}Yy|ya#>fFXbmb@e z@GSS`z37B*$lW^g2NAfhiiTeyz=A)KQOkfF7@!34>+05E5;KTseg3C({Pr#g_DL_e z@+$!ml!!lCn<08GsFOc3BbcTiz8wTX7bbWBBNF@tANJ3Hb|TolfPyV>Dv13p+9r@= z0WdSrvn}>RFvKp@OSs4YXhwLGZag*cQY3JFVrG$GHzHyQy!c=xBDx_E=0GbV@gcD5 zP@z05DrBkPd%TyK_X-_a7ZB#Vt+XiGh!?# z%OI8>NaXM^;h#jz$l^$%VN!kMA}l-XJD@w*2A`NB)C4|}AxjFwknYE6NTB}2pFzbA zh!ig*c8m=kk}~40fp>@G49XPn5uz_(q@oUwju$`5rYhIfWij%@L>5WC9_ zkxMA%oMT|c9*;>DJ;^PfIzNZ?P)4glXc=m3fLf)#q`35LNpnf?l=Yr6It;a^WNXYmy9rAR zq5{bkdC?!YuYIt5=Zl+t8^Q(xVbJD}$zIj%)ytTx*+=D1xPtMyvUU_ANcSk=PeOQ`o<;xVY~@%w4NL}Y#qoAqm9|N z_O_hIua8bopPn2ZaUON9Ngs_L@t<6;a`t_PI*Ev=^oWsY?4)uvw-Sh?rz9AKE}Qg1 zw;+js$NI}PP1)yZ3K1Sxf+BO+w$mYQj*$s6su!R)$N2H-#C6X<@jNOCimp zz$5e0uaI+5QjnR@BvY%<+$-QQRFD%;_$a(aKgI|B49e&O{ekfVThd07W*BW)W0>hn zO=6x>rqZuDMf1qIWT&4_X}74@L6I%rQ@{ThGgJ>M3$bdlN;~z#(~!}m7pqXPQOhQq zjFpYAOv+Kp{jx-5L{&%SC6A_ft2CzCR`B>uQu~WkiIllgnznm{Lx@AhH3vF&l0Xtl zQqgZCWyg7^d6jv0HuZYF`dJIoVrU$t z%-83|EO9N1EE_EuPRtI;4p|Sq=93nq=Gu$73n)u4%T#}H{9?$ToU5G5Va&yS#LZ+% zWkh2)!coELU_xPoVdk>E%_bfX)6+8WVp3s_=CEPbVV-7Mww^H$XRT)(XFB6BR zFE4RUy3dJ@kWc>_O`4xytsih69-k}kvhLBI_HKLuL)3|}i&2p+D=G!JPkv@#sYKP8 z-8kM*-+4w^tGlyYw@w@P;O%vlMAmLgKP&IObgYmiVCIex%QHTR_s=qncO#Y^mpdH-9L@pM`xplm_%J+9A63`e`MtQ}LeaMX^Svy-a84Y@TlWtA_ux+r0f_-6 zh7E)1F|#oMybt@Hi@tWD`kw2ApoAZkl;Kw48nQpKxI8S%zm`3!|F9q4S9qT}o%vOh zThl!&R&+A@dBky4bs{JSyQHevtRk_PmM4NU!|7f-$#Oo+Q3GHxag#mC+o^-E$ZOwy zB_tbVB0Vnp9^qaew$itPn9|0;Tf$OqS)Ni^+4Q|N)AO^IWZU)C?~i!^`~tjolt$Fu zVqawvyL^U2dfq|SxFelD9cnp2IoM*O)`i8awPj15T|tX>Q~MqTV7v`MNZe#_pgd6% zHmf=-$0l?m`}q0<=gj58XJvP4cGGg*vvIPm@&#dcqP+Flb@k$Ct<^{O#Ag&N3UVBA zo{*ha!FO)1a(eSs?Z*BD^^DRQ%mWNRFeI=s^n2)Ywg#{FrPWETKY)HxJfuC8QY=8s zL`S4O)i>?d!P#jN%YznxzOTG(`M#L6JF}ZY$x2}(lP<&OwR>ygL~Unre|Fz!Ih%Gd zbOEyo+g_O_pJx7{_r5(WUKul6TU}e4Q^Qy5P5(x6x4)uVP>Bdw0~7*w0URCp&l5N8 z&!HuV_IAdD$~)Nud!{G_*E zXm@STY9Hoc<u-Bd}{eSvhi9fBQWsI$5h@ zyg})G?Tz?k{B&Vl2tfu(0d5T&4F?Sm4|fCm5N#LZ6zve!5LLZmf-xF48?m@n5l@su zl|&Xl)*0B45HI9+F>*KeYyHNYaJ%*LZX+%-&pU?s;`Cyq#Xa|KtNxURGsVFYA&Xzj z`6u(m*!1=5b-=YD`XG&LCQTWqy6T+W@A^lT;j9_|n(5h#QC}q@YW2x$l^|TBpbTq5~UoxQklc zTC_c6?m9XPd>_WV8z9vYRbLDVWf9%r5qRpoTs+lmf8PB%IJ{GZsC=Qwq$nyMgNvSqq*o~V`X*V%kq)&^zo7T!T4V@7pHaYtVE#}nxguEUrh^C++zzKz@^HS}y7=<1s z_ed;Iw0}tU2^p~1r#6Y~P?*Q@NPPLJFe5$l6+2dRsBjO-fxS6-O*Y$fTW{Lv%1F|% z#OTQQscWR?chB)aOT--<&~MWQ3r**`$=@sd{t`pQzvQ-zWtC?ozLdT+uq1z4a~gg6 zoEu`8HM8~?O3ybB`2tpvc$ z≫VcE&-`HOph;RZ4eT0|^n`7JV%F6xpRpEVUUe7K0k`qX<;jBn*EZsSv)9?qR@f z`7P_S@pBWS=#s=&nI;7{32?f6VialzsXhOpmg0OW#oJV~oI_bAbtc_vuWEv7a(irh z-7BvvohxH#cj&@C=pQdAon*@7y=0?gkiV)FJQS`J<`pV`mdvQk90BLCmYIb4oY|e( zoB5>1q9(4!)L3_UkV=>2L&?8PuOhZ$>i4Czyb6!ZPw#lkitX;KSw4F31G}+wqbF#DhdUiQ1KghId zza-i7rMqM`Z9VPCYyNZ7QfsDtnj@P7?=jbQ;c3I7^_2D;Z+H7-;3(->!Fa;n(TRIM z?DqbS@>%_k^@;buOKVK?Yu4zZ3wZ`0S?*XZZ=yTyC{(~ppn;W1+wa5L~di0|MQ z;0F*g5atm02#p3Avv(R5q8l{Xg|VlqpiY8 z#DhhgMI1#3#Wtgmqa}Y}uTXT-S+2U3xmXFF7Ja>GVzD2+lDTqTwO<8mXr!D%*+C&7 zlOj8p#FL(p7?DkvW|ysy&{^H?D6pp-ow&?u|8kqC{iU~6$pwG;j%l8@p2Qgl8P6@v z6YGlWT8|8lJZA>)&CWPGOnojE+Uv2KB4Z=7y-8l~PjM$%hiFH&RxjE+c_a8~*iPm_ z-@u9xt?-NpPDe0CCq~|54YL$;z74Nub9+eurjB~2wzqm8qN(t{e62|YWG%WYy_%g* zH+wC<;(qS=3<<+W=*Z=QUszMNn&%&vc$~=ec7CwpMv+JOes~Oe zWiog&50x?<-523x(Pa3n1zzulOtow|K9_;pv0pIJ;d9}QN$g3B6W2N8JlvZ5O3u5P zL(Q3vHvrxVSCwxn0A&W9%Z@2+Qbor)lcW5}{&S6^m9~}OZ`mnaCw(Ul#~lmY^Nl(O zoo#^YRhnc~i^>|Us8+7I+-bSFs+q%ix102>`Z~*9=@99C>CSZT^i|DA4VMNUTV=~} z+qX{%D^KjjZvXX7@mZj*1z*Bc?Y`neLgFE%mS z@LgLQBU)*Gm)2$!aF?~Vht8nRIku;)jhF(Bd&XlT(Rz$16WpSi%lDI9C>4WHrU2^@mSV)dst9dX5In-qGJ)~DQgS`x-L-; zQDRXW1O-u|k?S6!-stzg-`Mt@r%o2^XPQ3TcEMeG9P@op(w(x)vbEd|Zwg<>UlWIc z=zL7`tg+d4un@g)wkW3!)d%yT;)M6*#qR;0B@8<>Ej+CmF@!MM3+sjI#(r?HLp@sk zz>4>KaB@zxZ~80khx;HPo1sjXr&G!M=~?;ZgfA6|6W|5-4d|G#oG6-n@Fw+jd{?=) zzHZ%nD85kbWO$!?ii2Pw_2_mWcHN#PImz!e=-$~vaUM1=(KFwo+y^Y=g!*h~4$x-M z7BOt9>1fI8{LtcTy!HTsZ=buZxfi zod+C2>{c8u)=IW;Z_4~O&mV;!w*OyWAMPKU1o^+Oiy(;l!TjEvtFN>{K&)^ofxi z(LZi+vg9REla?bAwskNjVxwoJXC&c+AtEB;aWFFBQVq-`5#yQ?#aXOmjM4E&_8GEA7_En z#RtQ~@b9VTgP{N%V}pPQfJll6D!GB4WkGtO^OOOr=r480zV?jzun-@3n7aYTKRaRIBnLVPxZ0DkN^4g@;(KM#Ri)6Z}*N|8?=#;5!wX| zn&6Re#8xH``Jd(`)-M!1ARwSd+I>41Q|bo_`Q9L*?^ygnegu8IR1)>@>(h<#WHzt* zy(X^3LfMyg&xhpHRIH~bKu-C%yGQ%`^T{udyW?oX7(7lA%?7KuU*A%sG&Ir;TT3~z zxSW}dms*@lmC7}gE86ch)SK+`XmvZ*lpPvZshrk#wq^dy4Dx;|*Qk%@az2)Ld%iRN zcz;ueSt^z%HD9XATP8q3i8t=_7OvE3|LOH~9UmWWu$fu(Fg!dQ(An$=kg~I@`a%eP zI$a=cJX@7w72@D#UX%ILT=Gff>a=?()EG%hN=u^y zrc9t#33xq*!qI7dTCX-l;{=6M$cqiqSai3+;~Z!<9)we<9=hJ7^(0}Y8YKr zOP^;JsS9ZesT&y?d8SB~utd2uS>Nv#7K4`YWr7ocw~eQ5TSs#9r%Un|B4acjK}-8; zpHD_kZp>M_FSuTBxrqHj6j@zqv)*FD9mLR9d~-043dDJ)MmyV~RaK1Lgl!XyZYB?B ztCUD}@HniDs}_qD)_mgP;-lSxkmC(~eIkNQwZ{0|E{Uj=GEfbTR?7fG_zCRRD-u9$81JYt9);m;!4T|-|4*L?Yzr_EgUA-q1g6w!x4K;SW9nit z6!VS`Cr}zc-yVs5HSlb-SvPt(Uq^^Dm(AFG5DrB^cT4`3LT@dUkK6zU3M&ue56gX0 zRvRf7O0?Nvo$&>cXVh}BBB{8TD!~M(6DIHWQ8;XSA-Fb-PlB|nr7Gh;Uyh1$BE>!X z!jQ$FdP`vuIf5&?2S5IoO9r~<+(*>IwdUG1M9pdg(ZPHZ&$S#q=zZp|7H*~Q! zNVANgYD0>}o0#FUP2H^IRWf@~ULg_i7~RFh#L}J6S|GqaNdIub{yVZntgLfx+>r1% zMtwv=A+1hF27NRtIs-7{j8NagM9UiBuFUA3=h{78)3}^1It0CL#yKbup;R+xQ7ThS zBkat_(8Uf}`C4H!8t&CAhtTrI7|W=v)9wfi2*mO%#K?`pU-O( ztL=uCOcs~1P!Vy6KGMb|YcKBE#MW?BL<9@0R{y{NOk0y19&+1!vL3)d=^V;|@V{Px z^b=ClrO(bJ%tNqWU4x*6LBGLC?VW}4G)mTjscomh#`!=Lu5`o1#@c+TDlP+^O60__ z&*L^^?Fuu`jG7+oj_dvDa-q&wc8Q#%#5hHYetZ74>p%uVExd?xD#u%Yvq8@e;(t%I zzW^CXWh{C)R@j|smLw77r>mdjP)`*Jz9b! z!rlPY%ileonOWP|oj^@XFrO`iK3LEQsoAlYgfb7=64O~Y9v?!@LH-o=CJ}mzPOZdv zA@8%sV25{(4X52ue4X?sLJP+REvw1Q5}ewZWDe^(1vm5gT;YtM8nC(&s>-w505lXP zcgAIpRt$uF9Bq?~Zs}*n!IVqy*p6}X2YY))2@5(tP&zQ$fpH&yqE8TLG*(a^J}8*+Rxmj-y(+xd!p|w0&Q4#!?B_!Lz z20dXC&i*ywNnO#B>FUB0|EEk6U66mlTfKrRi9g}3z$bSgTF&@C^@7Rtt4Fc-&l!r5 z0pe-#sNvuL3rzpRh=j=R?LY}B{00xFN;6s^@~6h}844->y~zJ;_zO|${m_Qd znVh=063VtWp#IaRP$_&uYGs{-nkqQKrYt1+qdO=H6$N;Jf`S5bxTLzH@))n@{T?+h zYQi684FviT60{RRy8>vVed|yx1^@IRWLr$2A@rV+;n05qPCxK)Fd&5AnUbO<{c~Hy z`V9gj0$#EHp#PrBet(c)8+$YI(?(y50927nl44=6CNZe1O$xN;GiIh;dt_KT{Sf|0tf0; zVK;nqI8|G~al|6>IX5M0!k&>r{Lf#7Qn7~xvnS8(; z7vf{5*rVNGIIp$nfqtt%=Tf!~Je@yplO-illB*B+(z#)Wrkx1GI&_#?B_QjKD z66IfpPB4x)Lg|5g3IOq4=mPIEHZuD8L?fRcbnM^r^81qOy8NVfcII)$IjHnbL@0kF z6h&#Pu((QEbs7!sE%E6$2{n`yW`6jACityRpsxv|(CT2OK?!~l&8X%FWS^3 zj;*#ynZN#JGIEH4YS~}t*Cj0>f%J_iiCQ^4e<8vPmYXIFqmB}Sj!_SE8uzzOQUJS- z_-E-RyBmh^lf%S~h-mznQM9Jm@6@qG4qq%_8_(K3*x~8~Z-p*@_rcT2D^MrWkdiwi zMT`AwHDZ&1tExibzJfwXXbUb6LH$uY@=%a(>uZ|?vWVPAzoIG}q;#5`5N3Dry;fj@JH|FPiwSqn zY(`L0Mmn)-3aSK6NBUUBjKX=8W4C^)ZWa0ReN>GX~)RY4u`D@qxu%#9evZWhw7iTQnv48dMW6Hpts zO5>ywBPVZE3c_hOhW3(7HD(Wp@fFd#7|Ps|^Ftaa6(k&z{pWcJo<{3=#wcaGjl33! zi8b5k*N)T#-~OJIU?Je!5T;J+^V;tOLCc1u#ONe=b;Q3^sl4igmy{hrkYT3bL!$xNWChldmf#H{Y zf5Xgg4OQsrlfmVgnOURp?oOl8>ZF;kHdl(7-Kd|IFsCVCRI#pknRk^(Q#*R z1YO^^`mtPKy_OpjfqtDwgQ%7>-tf*PAMjpb_Z zR`n)^*vi1yg>|?J3(tb}-RMCHAp##mJ6(TDOp-?HsB?Nz`Vr`>h`-#_*MI9?$9Lc~ zBbI~NgUQnOr~)xpmLURCQ|J40DH#RDLF&RRxV^o7jor3Tr4t$^od%iZLK#z!H4sQ< zV{{idv6zg-T2{6%l$o5KgOoYJ5qoL@Fj{K*BQQrNvbeR+;?Gv}-|ts#Ve5B;UBq8{ zTQgKg&zys9#&Y;|8?2V&7Zp9;zP{9-nRDwg7RcuCQNXR8e5N+R_Sof;ntS=y=HVEH zsS2<ZkO`)&W=LmS}22xv9m97#%n zPvpNNh)*D=q#Q2Y9ULy_*d&wXd9I3VyC7(`?6Z4vU9QPQxcl+u=}hix=jpZ=NI%MQ z{se%FI0S<!IFn`Ra7|lS#SN@mpMD>V8HB+g8I97Hq3=oB9(Hb+RBhjD8~!Qm zfhYbir>aW;U|M&s2lA=fn1s$HgV<@9oh^{*?X*45>*Sz({c@VG^-$=#kzallxIWV1Fu4 zxRAF0sS^$#o1=BF>y+pb4w5CmO-8b7+9qHDty2j!myM3%2tgM<{5xHe6KHtlyRq~J(6 z&vS~h!@reFBXhBMJ?h}_zE1rV&W196+e?rgtJSq_-pA<9ArIjFLIf^VAQpv}4@Ug! za)$Tg^=78V_?y4D3orn40HRgNKnVCf;KMmKPCd_?#VcCRxo)U_QD(dKWHw4BP!ty2 z0Rsc6dW-qLqQ&de+R1bSqE2xF_dd61UAOJeyIH|@_?!+u;jkFHe)@xGRO$Ka@lPz5 zYjU7oTbDbu>Gwh;Y{u}vQvt)X!i~F=#gxvEcg7kgb9IuEXjIcD zE8K|iuPYUcqQPb>v|EjU-qT^6ZSiZv{w;+57%*^RDP=YkHIb#OT#QTN=c)sSf@xQW z!eoAuojz}oOI}C6QjCBh>wsl=1E{I&tdJK;uAtX(jt2I@fj6MpY*; z)ShXy)h(5Xc4^v;=Kf9qMVZ5D9>2U;A z+sq4=8+3#t^zpe|m@6;e-}3_{2ibTUDtrJ$3YPN~*7w_;Zyq@wCa1drFUqqfRm)zUKAQ$u0Dm7`LY=iNI}S>+eX)#+4qUE9BB zJlD_JPE94&d&Xot4F5_=YuoSzST8plwyyD8)ZuY^h)|p`UG}I{B9o^e;LvJM@~ygM z`(|Ec!8JL>hM#}-fM1No4Oz2_o;>r_WUDdQp(Gs63k?0~J%|vWKS@0?k@>{?zBg-1 zmi4yEFjJ$9TS9=ozeLdP+gYYvEA@QaI#f+J$bmDEnVd|*R9&smoNo#%rtiEz5%=L8 z2rLxe@E>Ut{!!!c4q z-`DCgop!E8(Gy_S0=m0Gz90m-kqWhsH0Vj1W8LWBQ|H}+=BGILZKqA|hhbdXHe$Ydx3YlS|o}y?1_cva$d@zynv!NGPLY9cKli78uk80lQVImcuYPv(KwruhH>b z2}N^}`E+&@ACq5zC2}AFRuHJ7R!kFu-S~D(+sk!mMS9uYgNf49{fumpX`B)CT;j}Jym4^sd&thql4o3@knzC zztA}@y9I41BH==(aEx~%Eiyu2NDyLuW=wNTz9=LVj*m4A5@K5mrTWgk=-yz^868$_ zD^&V`H3B%Rd~;w{r4O3UaGrHEA&W1cVmQ-o=C9r|N-wU`D;|O<32_ZY==-d#PVINu zbSfUmp`7s^Hdbv%HhtfW!F`egJgSK4=~c2lydujMU!=+3-pkeNHB?s4NAGF1u4*p^ zJ;Tg!kmmvxPvCrR4{$^P(h_i>?IvlP=X6xkV5$1M*z`jXaw@Ss?zDL28kXKGFp zYLY5C)GSC9eM5m}4w2;3pir*Y-Mp&UVT0x3d8EPVTyy#5oJO{p+s>&=gA0WI5UvR{ zJ8kag82sb+^VSO-!HrT?h8yevG-D@nvgzf1mpL#Ykd1y|vM7~Vz|Z;kr@n&*p7tJ3c;@a<9BBx; zQ0*CnNgyO5`%Z)B!?_sQPVIWHrR>EyZ`%%1D-wd4@EjfY=!LV0ziDgL0(@aIUf@knH!F|E%EXWH?PMEF`=)4t5XRMT-I$lH^b8!*i zQWiN)Sn3cG&&l_uG+J%^)S0Qr;jI=W62fJ*BI|s8O*ox-`P`PY1QB!c{cdlkrRAbq zp8A+N%`CY@u_IpedA;s5-alm|iUX1D(@Dju_z=G@1KR`H%LB@Wn%gPyD^gD+zuHSQ z{(c9fn1@sLIqziL$2x1D+Y4YaqjX=FRQ!$`p^~*jv)v)F1mY1Hd)U%WRxfL_&amq$AFqUb(iZrg&i8^&w*Te zcF?~yTocOOC?`8mGaFGQ5GnXQ7u76{9EZT;khpvESBj2>3-K7Hjy#q~{=T*tpwMJI z-E_~N6$#-I+;%M$J3cHpZ!2zmc*;DI3tuesx%D|ykzmPo9(rG($Q78rDdek&uFnB` zk>_YF!nzaY)n6Wu3CRtds_&yvp$a(^HLI-^{3)HvLLqoE9#b6r?v z(P2_E2rky-o}y=b>4K3<0J#wVwskPP4xqtfPe6@1PbiEuug zlkZ4>Z7x%9A93S*LByhp%3x(zf4d+3e&cKMRaBgiF;IO8!j_Tt zJ7hCbGTg;cN4w`Fl&zR1V!LzG8qcZ9ayc@ZrAoQd)l;b?_gO}X&7>jo;s^bdAfsit zK&7K6ZeFXwQ>TdyQ->qq@O5*N?|q2uW2@a2+&4L|t(@HPvM>Un;cJA}&zHx*2mCgnLEzrJE?3=tiy9WiI`ope`Nti!D~M5ZuS*09hSG^ zga8EDBW*a>e&S0gg-GyFt9>+Wscv-$Jlco1F*s}^POQXGQzgBxqHgrnEA$6LJq4Z{ z?trxXC0?kB9th~Erx&3AjU4JRg~E^>M?;NMfi!9HSJ|Y(?4GXo@a#M4zL9 zfYF2cN7~1{pq*L`Ny8T2D|emNv0jQDf)=ST63JqW12Tfp=dnBJKyz>#odj=(aA)~? zZ}$~zP2g)=E#`(#8ACh6*a_5W%!zkjSyiTZ9IVUTF-L4TmtCXNa86+q@(7;t4XtCR z{~-E8hvC8Nngfn}z{}*LsxD?5N8vtI$-{4T>Tvy5*Nb=?E;I1e0!3)4Bk$6X1Ucca zOhTbKp7w2X)1WA?^K+J`%ansK5HD+4fGiHm)VAK+zm7rAFJ;n^9J#mEEYFXS`^iwmemba}i<{Z=+ zPKZ`%{tAeKhx#r1!;`KVT%6sF#um#JO7cg$IWjwJf=z19rDr~#ANW^?D z`H#iEK0vtK$8m4ALZUp3)PyD3XY+JpXX->IL5d(F)R9`sOvCTVNt{jm`^wb)^z`NChTs$Crwc%iFMF1LBB5g#-F5_5Utix> z3@f4KZWIFu0-i8D#)%27`N8Z3`j*qx@`uaQ{EZ2d@nO*>2O#Fb*B@KTCKO(mGc~Qg zC_ka%H@?|Z8=D=_gA1Y;pJ8rY3gA z6x_iru0DZ~dcr^+Bs?g~K|Q#(?WNEvbJ{KwQLwLoi*GrwFI-$sk70Vwy35k*@*7Ud2I6D4o=_Y*>Z)v%1NzTL#I?7bY#8ugSiMC|W7^9?AsXU?iQ zIv{tfwHechW3e;PY2t_>^ zHXfx*H6anV8?KsA67I$MCr6zbp<+XjPc$S2y!vWNa5pC1*!o+-A#hBKME8QPJ1YY@ z^9W54Or1E6?o3UA-BCcSEnfx0f>G0xX&Gh?x1;9=o{w=;UOwL#M_^vwFzD_z4|BuC zm2W^VjTt1RdX>*bx(Q(mxafQ{>7!dgT&S`)M4ecx5H3{fYbdQ~UMMr*(ZvkxZPWPK ze(uX5@lD$jBwGoKKse~q5H4EJrnGcwEyISu0)p${jY*usmv0y^^a66`p6|korOJOk zUONkrl2##l+{{Jkde!s!pd&Q6NbhXLH8vw;gG72g1SvuT47 z4vGle6Brqd0$MH?)Q{6by2OSWYMXZenGmHk!h0IqBX0esR*emugu6!or*=ega&jpv zudu|~i^ke*j$-jM|7&0_ZJeG*7U<+1*xek69UAd8zr5jSrId#*J$?20J16g-PlEI_ zV6XFQUp}=cXeQA5N;0?KEfDS2(c0pzPDB2 zBB}xO1#!#Ov1Q1$(3;TR@@I?@^Wffm#fX+(+^~mBnO?=9=G28YZrxHy}qk@R3Ix0ukxL+BAm2z)t{de z1fOh8bq5}#cR7KMoz!c}0IG|eANbTUPq?Z+{6frB=PbXzFdDhK@6{p3;Z(Qy5%tuq z&tpHimFjRN4e$H3UqBoYNvgL4lB36Pwhcy7&`2X(K8SG6ta{?Fpoq&VB7=(bUT9`4id$e?dXaHn~ zj;d7uB2)YWNVj-Zjk}Yo*G!K{F zZi2WZ;)(N6iYC!zR0TB~oQ#q^g!&eMdi!d;JPiN0hnE|Jk~>_%f!hJ!E`-W*%DyoB zHqc16l?>9e;f~)d+Ly(NB%ye*$^`#|H`va2EafL92c*H;88RrTi|}4hNM4Zz70bbC z$mPm46h7)dK_nVKkoG8Ag}WK3GDG39Lu>B85V}u7$>8*Ci}w1(8E(vp5+6Tq;D}8v zf>ohKn=#c0TMkCaWvCkOsOTQ(`AGeRU>gc=S(t_*#f)E13R(Og-X2kDeT3 zG%rrT26~H0qAl9tThtNVrzS-5p-DOnDfEFY(QnXn;M9$j4*RPnV|5*{mkkR8MOn|#W(g91;S>Nm8x4CPEr zjfpU=+_}Qo@bZ$|X2qRUNCXG+3*_D(UpaW1#0{dqh47g`Z)h4)Tg^Hf?-QXDiQa$^ zf9Q>BxXFM7e!=D{j?b&aGLn?#CI9hUgjkzEpH2`|RJ;d~OrUrDcqbotlWfHD+=K zxCF3pF7tkO#`6Slrj_~I6hd>Z7q<5f8*gV(8(dNL{hwuSTbFR)Yr3A?I9Iz=gq#bR20eR8l=k!{ti&5It>36^-jN|dekB~{Ik zeG<@3Vx&Z1S-t z$F;Dum?tfkic%&!@u%W2%5Q^QmGN{G*PS3dP7l^^^S$-f`M*`iYk2u_r=WFO-8nwn z_z+#I#X#pK%-7gkhik|D*k>T_+}%gkq{|uq_qdbX369UwAjn`%2RMtRX#hnawK!C!>k}u-|0JOx zll524)2Q;I4o&;y1t~FcKfjdGe)xWk`L0;=^|58&8sznNDL6|p^F1&kL~>Am@~tS( z>YRN2dI_Q}pt`g)fjf{ooP}!kG)X==o@Uf~=cK1o&ldX771af1#Ha5_sOEWnHs7pH zm@Cm-tR7e0?27PI<844{G#*Wqr^8MBRZOmQyHKnk8a>d5bz#HiO{kCBqmD4N8}f+y z!<{ESG)`axY7da!+co7V%lic>aNYAZQAWFE2$xiFZ)0vcXOL z+y(md)~LH5URp8XTKJ@&b&KFW_u(o=M>k+~*H-G()Y`Y4ObBaWK@m-k*P}nr z^%5$x>x9*Esr)bOf!+l5>+6+D{*QnT1z=%~q>NPjq?6rC{yW%Dmn^R6-`nZw*ZW51 z3uVnthjWtbHfjvM^cqIbphw4kfl0LT3Lf`d9OB-79uu!e;$L+00*-XQ%H-P~yfcYM z6LM2v-d`|meorGQF)u;+`7xy$nkB_)tdqfRP5+DJ+i;Kj&DfUb=tB9p%LzZDdW~DP z)A`JNB4!SU?TV4l#TnQt)hM@ZN8a5T!yPV~&z|ME=IZafoDLGLWt1}a5|U^-Rg#ec zMiY44lue(sFV(=LaH9?H;E~Ju8nN#8bSj3n+i+H!nZD}v#SJpcuvuCi-Dnt-;|<`pM&2fPfns*ns4rDHF+l8Jh@%@7l{cLDs_lk8*Jk? zFcD%eFUJ@kz&u??uYX1CzrLq%HgKlE>#mUBn0~9rVf!VRa4^xT?X%Hh-cFnSk|A=j zN@_fkoM6-bEKz!&br*7?4M8uPJw9L`!%tL@bj^UGsy7bS%Tcm0oSZf zkL%Sexv`t6!)$zw$-Mh=v6qTKq`V-Qw_^olHxz)y(3MKW{AKM5ASObe$hK<1VP4+l z)?REU;L~DbiE@1JOETw&{O?5QtSB{^_qh5~kelXw z*@uChDeuOt;1Dx(EN`mllaTipDZu|ws1mnNol410#ukXjq&`qR_^j(TJD@{HASSpw zeoT3b|8gHqj(%r>I3|uK9+;LDbniA>sO%itSJg4jnrQ0*U8r_6b-y33zTP%XfZ^4M z5?WlqQ*(oHbhxn`Dv%Os$HOd!L72Gp(ed4tW_}E(!7t*)!l!%Ka1MPfz}MGBZ+Wc2 z<3l0czdMLa7;;wnzL~f zygphg13{bYx5_~=4){@Wlx5VEvnmmkQBb-EiBqGM8qI9ytH?3C6$x0yYmSvprLrj51RwXBGj*BFov{s>Ik*y7@JhvBYo_~?CzLLdHM#vSifc(cf=uYOyD z=V_EVu~=_f`9_lN0=(^6tu8DDJr^Bs$<5;bpj#oQwOU>9-QSW@zK8A?<~0uaePdwZ zuOV!Eh;}+(n-7xQ4SL}Jst`@cZ{w4TO!3yII2p!f(5nB&wX43-=vv7MsM;poYvaQl z+7=G&8!^2GppJ7QC423&Ev6GzHZ`fa1EM&Fp1EQQM2gO;x5^&R%A)G+MMB-uNRiP>#BXoAFfCk zIvcyf%FdTADY)QiT5|W?Y3}*AS%|PZWObQadaR_Cf~l6PNaJwW&=Px0=N3HHhcGLZ z$_snsxOQ-&V1DhvwrM|eNn`R(*F&S?D6l_(}$rpmMoOdaF%qo}Zr9uJk@?FJIoL!LK(n>h2%Mo##k zebF4?{mA5bUD^fGZ2u<}8lo6=n8UF;U)9@9&mBB7L{rQ6;bUSSE*eL}B-qi*gcUoa@jRPYn@c*gw5a4-OvVt-@aq zSXSbIMp+U(m1(xB5O_Sw-xNf|oi13f9>>@yx*N?&{D_H2D9ZK}Y_M7}BT=NiDg#@s zaT-QJbupe#s{9M$$z?(}opkEkUEHba#sLF$u@@uwv3BQ`xsnyg607s0+0L|d>yNWd z<58pSfF}hYNxEwueAuiCNlABs2f>F-{Q}q#HL(swc3m@Xvw-sTw(L21ewmW$c=HI) z+-%H&o9mWQ&8xw1UAx)-(R%@RzHi&fBnYVyBZYoOqrch6)lV;dv)*Byaizp=xuJF5 z{2?g#|1@*fUs1N*9#=p@TBMs10ZEk_q(eXi1c4d4yBSh(07VdKk%l3pJEa>OfnkQO zK@f?dyYr0Cd)_#Y?;mh}yVttbz1AK3ioL&|?>41ApWl6bonANaQ>Hmc!Ijw@8GYg7 zG-rdy!a=)>KKO9utuIetJ}f@LS{)$vW`fofs_TFiXFtBDn8a3)?$bFrXTiGX>*jcD z$BL|}Pa{B}(_rP`_3cT8yyuoI4AzroH)sN^b%e7?GBhuAlxzW~7Qbxox1qP1)y}vD z5A=VKPQ%9q3&;8JWEnJgXC6UT`X?+a+TL1kwR_Ca)SVRxqx>BEL1a~o6&XQ@G5 zZ#J=qgtW|gOB=@v=(CsI@L!bjTP3bv)|YsXN_NXV_RI^L z6I4W81D!9&?R33Q6F+iu>Uyz+{MbtZeFf z3GS+fSgjxjQ5U|btO6|Jo})cC?$@r1c+QM!bi;d(U*1n?p7mShnaYD%)Aj9iiJ5*c z3P|j05|jZvZcF8eo6TS&dNlz4>c08xbm_cYeM)iwgYs)L4BfBgCS2JzEeK~7#$^A5 z=R8lY@;Lu-tm4JIu_j}dxm%KrYkB!$Hb0#;Sn_ySK0i4!c^(5j{EFm(0 zzZ%ywYwMlV&Y;3@Q6yQXk?5qq#@IS3aj(?D3SGnU*|n+?b4#gVd27S$=BcENOLG}u zP)lINCyTN_Rn#d)s>z2wdYjj^*05n|!JIB=%Zg=cX^8etWY0%=EIwcYewi;VC6nlCv^9D=H z3^c@I0AE->yV&|9g64eHFnf9lvBz_~%AV7y)z*oc_Filx;}iyjE&b)K28|9Ty2A3e z*{85aq`@k#)YII#H|LSfkLK0sp=jnk*i#k$;f`B`VkFaLrgh^a)1B_YH*bNEq`vak z27CDjEj!td&wPovs1RpQRzTU8*JqH*LLWPoya38s6lV$-e$hi)ngBYd_8a(}>6-}! zj`L<^5BH|4{HjYvkKT)ka`DpZY1ekAJVplX%T_cNg%@88qS|GWFBHjQ%;+r1CB{{(+gfQfwC9psz3Di`*u;rm zge|^*$9@JKJoP=PW~9LpZ&D_&CYmSkmJ1V98Czl#INq2i()WsIy8)%5+p8E8`-aaiZ4} zNF8&OQpp(lW)$wX9;fV<$ltraPOe;AP>rygsu7g_)UvkO;=RIbbM0fgc0qlawc;h0 zr}7~@GWN*$brOmq`g7AmjK!RWc^@{a=G{e6a7o%+QuR=TdARFzwaSa(<3HOt;2E+ z?&tiEWZ%<=3+_a;1NcbZ878nR60;i$|1LW0h~dBv=F--kwowi1ZS&#>xby9SN#VnA z5oGEUQ1&rv%nylzq|D2ZC)=%{zBRM^_yAD30Vl*3m5|pML%9(kMj9)ZXlg#YAVc!V z#y08YM~JZfv<`=-`mM#A>=5W&>r?LRv=7|f?VL^sDog9h7)Gx~gaCkr@^qw3fdIh5 zSQL6U1UN#WGcL=27L;UwTNx>%$i|LZzw-IA%0cO*P(RkN%qe6sg3Z0VXM2*006e_c32Eee;8aqYJ{q{6;np zdKm9cXP$yYv-;aLPoE4#4qZLSPBo%u;@n|Flg=Zqo6g#J!X|yRuGMmaLWJ`jrp$IG z74GHd=B>K=#~fj<_HS6qKuw2~>n%@&{5|Qiagh^+ia`Ae>6 z>07sE4-J6KPH1vXNZpncLWD9O-g&dy_Sl7L_G)0l6s^5{K|@(Uw8qW*y$6}5CYR+1 z_>^>(k%;&T>__k1iCvpw=GgzL88@J88wq< zXJqyA%D0P?b|`&4uz;@C1MR-Va&BdE*3Zm_V!el5TM5-`qmO%x-S9^6A*M&YO}7d8tqZNQ4gvQ^`h5dW zJ`g)idVXpeOWE!fgv85ZG|LgLItZ9w_hrI%2WuUD&o8k~4w2F?GXIv4bvaR{4~X|P z7wg}E={Z5JoN~L0rSSU3Y@H1A0A(`BB=e_Rj;sErY5NI`*P+H_)tGl3H2!TA%OOb8 zVMFheL322hu_L4D?_ym$E8*g3z&kfY@66$xgQ5~}`Evqym|XV<1ht1IG1~|ACi4`+ ztv0&)gT)zf8vDwhlz0n~6ULS(WH6~=F^=U~nsw5gefE2uiuq&wVv(*dPW1Q+yU$fg zM)gK&!8@-Bx@5WKVWo3~i}sreb8wdrPR$O3xku_Y>S2#X)2?ESr72>BO4@L{T;rvt zDVO-1&o_Iv`DtROtETql(Dn7=0Hy&Vr)zec^XF5jFC#^X;R`5+IsE{8E1F=Y!{*TFon4DPxeI7HI)wS6;_B%QN! z-!8TJ#*PD^lh{e9BJ!xbOoNfvf*1Z=SdP=Up5~pxhi6IwSrrjjoH}PyEffP_EPRpm zi~b8EVI}wRP^c}T@$0mfr8kvG`|Do@=-X#wz#5J^Otp(=gOq^GDm$3crpoc$hU(04 zp=5elEfm-QW_zFt`sO&CT}$NtEs;|6^otluoO4-y0nV?KXd3D>_NXLh!=a4d#V(8? z@1|ziZu?qg`e49BZMsj@Qm{ECSOuASG`Fk$E%zW=)5usyCXP^ zYW``inytWxc@h$4!U!G91N!|2ilYe1{qp+(Ti~C!%|TnsVL(hT>USpaa~%&GQVi*2 z>ousJ?nWkW$V5POsN@1&@iu`Ro+giElp8~48_vzQZsRjo0vj`xUBPtG!y>e74(@_* zzlwlnuQF7;1GI~vv9PM+Rwk!Uoo7>+3Gv~qu4eK>sf_)& z*fV(@gfm*Uw~X*Ha`wetOZ90z9cpoK60j~d*P_Db*Mc4 z+6}3%Q{}|G!b@3|Az z6(@OdrCd93sI2D7LU6Pt3gM)D^vg*^XEH(HB@#hzQn$z2VAj5Le{N=ZAx%(*Rv^e> zthnE?G38hPf=Ns$OZ}X?N3htB0(O&=D@zx|pkZh~79$59S$cj|t8=lb=J%?Jxce&4LKfznpUs-llJ)w%b<%vs*nD`w`w$6@&yvH2OkGm?OzXQ3~oEF}t} zl^>YF$Rd9qhA)D!hhfGo_|Bp^^#ayb*|!&P{cyd!W<7J?<_B2gQq0$J!K;Wmm|L$4 z&Y=aC-B~uTa{zDY>w6$wVkkLWXIUXwCUU`aqm31lhDIwgk+$wVqZ*G;p7tEKZRrXZ zQzv-Lz9mE#-tofsjAGA!@w@pUO{*0$+Ao*iu>ns0KKd!M^6TySg;5!1G-XI!-ClHDSsx3XGXVl2s23D*)K@Iq8TAUQ{^JB z*1n~NreFvH%GpQ6$eC?u^gPAv9A#wk&N3t8JcIQ5_c-pAS{k?59Ix;hy^fPUS3D;w zMab3{Teej4D<~AXmzp7kY2Zq8IgWMJ#x`$^6q+fkTu24lQ=>ZANU}5ANatazyFPxt zK~6b?wdVXUvmK)3eOx#6lG`o~f$k5+y{*RUzV}l-jx3v{YMQrsNBx}L<$PUx4rJt2 z8_{^JIkMY*D})ifW&C7-Jqa}5C#k>kZOk3!LOdaOq}tNK{`tOOLS`q0-`%|V{`VEX z)YtXY7M4p9v}Bm_B2?G=4nsqwt`PGjVSjp->3{^jnAuBw2F;z(Fjf^mOi`bxi+Vgz%D==mzN(eRk9^?D|mFGiNy3=;U)B*^N zXqmpfd`zVojbtyOUzrYY-7DC`dv(eXdTrkbwEcmfZ1JS-H0k4B8wY1#>NVqbGlq^C zKKlOA*LcKkSD>F3Me0t`bXP`6PkPDi#RI>-x{=bHWo7se+X&ksI{cSSJ@5aesrOc zWZ{_-C|;+B19X@} z#z*F#T$rxL8uFgEy?Bkp;|Asbush_58|6dJ$ztoAZPD7^oC)zMKU7oDxRdp z@v}~00uY0jMQiGRl1G2qWZvBpb!N6((97CljmJY)miP9A!8qym+h3uD8L795yw@a6 z=(;iLbw9Shk2pzQveGojzv2tFrXMzaH5U1l+mcaFBP4(75ufB3Cc8hP{p9B%=5R<+ z4EFF?Opi7CU_O|3al?d`aQVz2A=SSkBrIC+s&(TWA4Qyh<&u)?R}`Pj+Jymji9@1W?G&k~r5U-hwsL!u$+U)&TGEO+>#- zs!?l&cxQ!N@v!iM8lT&b$aLQB5J#>RbKGUX&7}}OTG+t2AF@QBbl|9;t{!K%5$#4p z8A+^z0%zJ>GyakqI=C_{LXvpOMMB3P5KlHT)YKjsmM7)C(=A}%D8(QQ&TpSl?|;c6 ztr!m#Og&7SJwF%<9bd@3UEF-PQFPd?QZNd(c%b#bbdpITe55!9xoY*7`GZu9!Z z!10gTkti(#3CN>wBv_`P%oM(emu%Q7bCbiK+UU?JfkzSVw@TNCDZs*iN2= zSt3Q&bFKm89pS7uW~=~S(8zsqmc7mbp3Znm{Li3$Vbg!UtV6$gY3ph}qCYZx4LU$#5n0}SBR|@PSpE*cRWyqC<;tK~^XhWe{ZS@lZ0952!d)XvQ`!bP!gd@z^7RKJu!H!PfoOE5UlYK_;D=iu_^PvlsF%)lRt8j(O?K{N$0x0nLt1~}PSiUzW9aoy2KvfOL@ zpv&fF&HQiCKC^&Gwwv8*YK|maj;!sHtX!AaV&4NRp7%eyF%fe}vRv|-7)t!UjQCq* z|Dli}gx8zh1G`mOttX}m`EV3H^#T^ne}8=_w;U^B&rGai&Vv8cy3c`-OcCgm?uKSG%;08HP8PH&!;^%RboA^H8y%#ftJ0?am1`$h~ zL7jkh-9+MO5tI%g-lsUt-m=S39$(@huS^(D`U78bwq}YbO-KQG6JK`0PAk2?qZYC_N}5_Yjle z^7B6*0}so!gx`?RRQ+?v4Ld{}#Si&|thvLDgN<>e8|nG~WY+!-#c+#bhi<_WfPcE_ z@7@dwq-~_9r{5c2FYjH#6^w0iWn{Ovw{LI>0fdtGZy7f+!JX&6>WY?_axsdPB!2#U z7k-pByD{1N<1?=HRI|IKMsGvL-(eb+_FF+OXwf(>FO7`S($MFU4XX);_wL>69=)DO zmg&c)F0b*!D^ZfXrRW+dOGfF7+C|Oes{x(UoodxPOiX;l%L8#(^ucwn^Q*^FpEdB? zSV)R(I%j$7Zi1v6%J@@C!rB9(y1zq2H;5LouKQ!*%rz}7?XMdFZ)?;hT!x#K)clT1 z#d2&0s;z!zc4!xRSSO12f93(?9+K1Cy?al=h5r5NjXjD)MzsV!o-s$A zV=!G4BAD^tYui75En7R5FtLH$)F}XK^??d9v#Xnbi-p(}azQ1`4a3@ct#SX&S=eZi zv0-Ot=RFRN&PrBS?U%-{t*EG|ma3y=K223aAG6H8W@X~RVj~ADlaKH0;{FkFfoi|k ztjdeJhf-3PZRGiL{7GV<`Pe+7O$wzfy@Rrv(O)A>Xd0K&7NZc zmDzxHCPTSfBF*r>ij@Cn#s*zb5uWrEc!X2T&h!w|_Qg*a@eZWa#ppRtf6rwYPs@Q# zr#WrIq^ht5H#zV@|; zu8o%RVg*O^E-+tgA9KZy&G?b4&ZG5Vqop93e1-b|5-tkZmjwpCE%5rJ5^|B$5AkyuIXP8* zee0*H4$3*BFe@&zHLAa9nG(zjb~D!0D>dS&n|l?GE23xn)esD>pK(8K*&7Z=r4Ec& zqFRMCSYBJzTpV&&Q0BkqG{l9%gf;T??LG|5>d4h9O&=V3GUikMZ5%_z9!K|FUBChoR ebJcC&*a;BvB*bdq + +Sample CGI Script + + + +

      Sample CGI Script

      +""" +``` + +Now, once we have a file we want to serve, lets start up the Apache web server. We can do that by creating a new runner. You can create a new runner by clicking on the + icon on the right of the tabs like shown below: + +[![New Run Configuration](./resources/images/newRunConfiguration-new.png)]{: #NewRunConfiguration} + +then select Apache httpd (PHP, HTML) + +[![Select Apache Run Configuration](./resources/images/apacheRunConfiguration.png)]{: #ApacheRunConfiguration} + +You can save this configuration by entering a name to the right of the `Command:` label like shown below. + +[![Save Run Configuration](./resources/images/saveRunConfiguration.png)]{: #SaveRunConfiguration} + + +Click on the Run button and the apache server is ready to go. Click on the link that reads something like: `https://-.c9.io/` and you should see a browser come up with your folder listing. Clicking on the `cgi-bin` link and then the `test.py` link just shows up the text of the python file we wrote. Now that we have the server running, lets enable CGI on it. + +The first thing we want to do is to enable CGI mode. We can do that by typing the following within the Terminal: + +```bash +sudo a2enmod cgi +``` + +Next, we need to tell Apache where our CGI files are present. We can do that by editing the `serve-cgi-bin.conf` file. Do the following: + +```bash +sudo vi /etc/apache2/conf-available/serve-cgi-bin.conf +``` + +The file should read something like this: + +```apacheconf + + + Define ENABLE_USR_LIB_CGI_BIN + + + + Define ENABLE_USR_LIB_CGI_BIN + + + + ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/ + + AllowOverride None + Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch + Require all granted + + + +``` + +We just need to modify the following section from: + +```apacheconf + + ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/ + + AllowOverride None + Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch + Require all granted + + +``` + +to + +```apacheconf + + ScriptAlias /cgi-bin/ /home/ubuntu/workspace/cgi-bin/ + + AllowOverride None + Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch + AddHandler cgi-script .cgi .py + Require all granted + + +``` + +Save this file and restart Apache. + +Once Apache restarts, navigate to `https://-.c9.io/cgi-bin/test.py` (replacing `` and `` with your workspace name and your username of course) and see what happens? In case you're seeing something like **Internal Server Error** we need to make the files under cgi-bin to be executable. + +You can do that by typing + +```bash +chmod +x -R /home/ubuntu/workspace/cgi-bin +``` + +Restart Apache one last time and you should be able to see **Sample CGI Script**. \ No newline at end of file From 2f29d7dc604546fb657df94b31e03afaf91abc68 Mon Sep 17 00:00:00 2001 From: Gabriel Farrell Date: Tue, 17 Feb 2015 13:22:31 -0500 Subject: [PATCH 28/33] Typo --- src/getting_started/create_a_workspace.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/getting_started/create_a_workspace.md b/src/getting_started/create_a_workspace.md index 991511c..0cc1130 100644 --- a/src/getting_started/create_a_workspace.md +++ b/src/getting_started/create_a_workspace.md @@ -18,7 +18,7 @@ After clicking on **Create a new workspace**, you're taken to the screen below: ![Options for creating a new workspace](./resources/images/createNewWorkspaceOptions.png)<651, 151> First, let's enter a workspace name. -Depending on whether you have a Free of Premium account, you can choose to make it either Public (open to anyone with the URL), or Private (only accessible to you and people you share it with). +Depending on whether you have a Free or Premium account, you can choose to make it either Public (open to anyone with the URL), or Private (only accessible to you and people you share it with). After this, choose the type of workspace you want to create: @@ -39,4 +39,4 @@ Now press **Create**. That's it! You can now see your new workspace in the dashb Now, just click **Start Editing** to get started! -Next up, read how to [run an application](run_an_application.html) and [set up a database](setup_a_database.html). \ No newline at end of file +Next up, read how to [run an application](run_an_application.html) and [set up a database](setup_a_database.html). From 566986a4f684090462fc43c78a93f0b1dff76f44 Mon Sep 17 00:00:00 2001 From: Mutahhir Date: Wed, 18 Feb 2015 16:01:46 +0500 Subject: [PATCH 29/33] Close tags in python script example --- out/writing_a_php_app.html | 1 + recentFiles.json | 2 +- src/running_and_debugging/running_python_cgi.md | 9 +++++---- templates/default/toc.jade | 2 ++ 4 files changed, 9 insertions(+), 5 deletions(-) diff --git a/out/writing_a_php_app.html b/out/writing_a_php_app.html index b4b4cfe..d920ae7 100644 --- a/out/writing_a_php_app.html +++ b/out/writing_a_php_app.html @@ -121,6 +121,7 @@
    • Writing a Python App
    • Writing a Ruby App diff --git a/recentFiles.json b/recentFiles.json index 66fc59c..29f5ebf 100644 --- a/recentFiles.json +++ b/recentFiles.json @@ -1 +1 @@ -[{"filename":"faq_general","mtime":1422453385000,"pageTitle":"FAQ: General"},{"filename":"setting_up_postgresql","mtime":1422453385000,"pageTitle":"PostgreSQL"},{"filename":"picking_a_plan","mtime":1422453317000,"pageTitle":"Picking a Plan"},{"filename":"frameworks_wordpress","mtime":1421859765000,"pageTitle":"Getting Started with Wordpress"},{"filename":"deploying_code","mtime":1421769253000,"pageTitle":"Deploying Your Code"}] \ No newline at end of file +[{"filename":"running_python_cgi","mtime":1424257208000,"pageTitle":"Running a Python CGI server"},{"filename":"ide_preferences","mtime":1422860320000,"pageTitle":"IDE Preferences"},{"filename":"faq_python","mtime":1422860320000,"pageTitle":"FAQ: Python"},{"filename":"faq_ssh","mtime":1422860320000,"pageTitle":"FAQ: SSH workspaces"},{"filename":"faq_php","mtime":1422860320000,"pageTitle":"FAQ: PHP"}] \ No newline at end of file diff --git a/src/running_and_debugging/running_python_cgi.md b/src/running_and_debugging/running_python_cgi.md index 5a60dfd..bbe8b3e 100644 --- a/src/running_and_debugging/running_python_cgi.md +++ b/src/running_and_debugging/running_python_cgi.md @@ -20,8 +20,9 @@ print """ Sample CGI Script -

      Sample CGI Script

      + + """ ``` @@ -54,7 +55,7 @@ sudo vi /etc/apache2/conf-available/serve-cgi-bin.conf The file should read something like this: -```apacheconf +``` Define ENABLE_USR_LIB_CGI_BIN @@ -77,7 +78,7 @@ The file should read something like this: We just need to modify the following section from: -```apacheconf +``` ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/ @@ -90,7 +91,7 @@ We just need to modify the following section from: to -```apacheconf +``` ScriptAlias /cgi-bin/ /home/ubuntu/workspace/cgi-bin/ diff --git a/templates/default/toc.jade b/templates/default/toc.jade index 3a5b702..23fe325 100644 --- a/templates/default/toc.jade +++ b/templates/default/toc.jade @@ -135,6 +135,8 @@ ul li.nav-submenu-item a(href="installing_python_packages.html") Installing Python Packages + li.nav-submenu-item + a(href="running_python_cgi.html") Running a Python CGI Server li.nav-submenu-item a(href='writing_a_ruby_app.html') Writing a Ruby App ul From 9081ee01151d09dffe4eb92d16d0e0ba1c15b2ac Mon Sep 17 00:00:00 2001 From: Bas Date: Thu, 19 Feb 2015 20:27:23 +0000 Subject: [PATCH 30/33] updated mysql page --- src/persistence/setting_up_mysql.md | 90 +++++++++++++++++++++++++++-- 1 file changed, 85 insertions(+), 5 deletions(-) diff --git a/src/persistence/setting_up_mysql.md b/src/persistence/setting_up_mysql.md index 856ba91..c604c54 100644 --- a/src/persistence/setting_up_mysql.md +++ b/src/persistence/setting_up_mysql.md @@ -26,7 +26,7 @@ $ mysql-ctl stop $ mysql-ctl cli ``` -You can then connect to the database with following parameters: +After having started (and with that created) the database, you can connect to it using the following parameters:
      @@ -40,7 +40,7 @@ You can then connect to the database with following parameters: - + @@ -50,12 +50,12 @@ You can then connect to the database with following parameters: - + - - + + @@ -80,6 +80,86 @@ You are now in the MySQL environment and can start the import: To verify that everything got imported run: mysql> show tables; + +Some useful CLI commands (please note the semicolon at the end of most of them): +
      +
      `Hostname` `$IP`The same local IP as the application you run on Cloud9The environment variable 'IP' (type in a terminal: echo $IP)
      `Port`
      `User` `$C9_USER`Your Cloud9 user nameYour Cloud9 user name (again an environment variable)
      `Password`-No password since you can only access the DB from within the workspace``No password (empty string); access is restricted to the the workspace
      `Database`
      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
      Command + Description +
      `help``list all mysql commands`
      `show databases;``list the available databases`
      `use c9``select/use database c9`
      `show tables;``list the tables of the current database`
      `exit``close the mysql command line tool`
      `select * from mysql.user;``show all records/columns from system table user`
      +
      + +## Connecting from PHP + +So now you know how to create a database, start the db server, access it via a +command line tool.. It is time for the real deal: accessing it from your code. + +In this example we will connect from PHP: + +1. Create a new file, call it `connect.php` + +2. Copy/paste the following code in there: +```bash +connect_error) { + die("Connection failed: " . $db->connect_error); + } + echo "Connected successfully (".$db->host_info.")"; +?> +``` + +3. Run the code by a right-click on the file tab 'connect.php', select 'run this file' + +4. The output pane shows 'Starting Apache httpd...' + +5. Click the link that is displayed after that + +6. A preview pane will open, showing 'Connected successfully'. + Note: MySQL socket file can be found in ~/lib/mysql/socket/mysql.sock From 465737702fa2f0c876f8e687ca72ae05299e51a6 Mon Sep 17 00:00:00 2001 From: Bas Date: Thu, 19 Feb 2015 21:54:50 +0000 Subject: [PATCH 31/33] small improvements / typo fixes --- src/frameworks/frameworks_wordpress.md | 6 +++--- src/persistence/setting_up_mysql.md | 4 ++-- src/running_and_debugging/common_errors.md | 2 +- src/running_and_debugging/running_wordpress_on_cloud9.md | 2 +- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/src/frameworks/frameworks_wordpress.md b/src/frameworks/frameworks_wordpress.md index 18cafae..3b862bc 100644 --- a/src/frameworks/frameworks_wordpress.md +++ b/src/frameworks/frameworks_wordpress.md @@ -1,9 +1,9 @@ -# Getting Started with Wordpress +# Getting Started with WordPress -Wordpress was made to be simple and Wordpress on Cloud9 is no different. Here are some key docs to getting started with Wordpress. +WordPress was made to be simple and WordPress on Cloud9 is no different. Here are some key docs to getting started with WordPress. ### Run & preview your WordPress site -- [Running WordPress sites](https://docs.c9.io/running_wordpress_on_cloud9.html) +- [Running WordPress sites](https://docs.c9.io/running_WordPress_on_cloud9.html) - [Preview your site](https://docs.c9.io/run_an_application.html#pre-view-your-application) ### Build & access your database diff --git a/src/persistence/setting_up_mysql.md b/src/persistence/setting_up_mysql.md index c604c54..697bcbc 100644 --- a/src/persistence/setting_up_mysql.md +++ b/src/persistence/setting_up_mysql.md @@ -128,7 +128,7 @@ In this example we will connect from PHP: 1. Create a new file, call it `connect.php` -2. Copy/paste the following code in there: +2. Copy/paste the following code in there and save the file: ```bash Date: Fri, 20 Feb 2015 18:48:57 +0000 Subject: [PATCH 32/33] Changed FAQ about Digital Ocean whitelist --- src/faq/faq_ssh.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/src/faq/faq_ssh.md b/src/faq/faq_ssh.md index 369b601..2a12fa4 100644 --- a/src/faq/faq_ssh.md +++ b/src/faq/faq_ssh.md @@ -5,10 +5,7 @@ We recently discovered our web host is blocking connections to some Digital Ocean IP addresses because they suspect they are being used by Iranian users. They are legally forced to block them. -Digital Ocean maintains a whitelist of droplet IP addresses which should not be blocked and our web host follows this list. - -Please raise a support ticket with Digital Ocean mentioning that you would like to have your droplet IP added to the whitelist. After this is complete you will be able to create your SSH workspace within 24 - 48 hours. - +This issue is the result of an error on Google's GeoDNS and they should be contacted about this if it persists. ### I'm getting an error on the SSH install script: "ncurses not found" Try executing the following command: From f6abe68a8559f3e98d341dfbf157341618db2b1c Mon Sep 17 00:00:00 2001 From: Henri Yandell Date: Tue, 9 Aug 2016 15:08:52 -0700 Subject: [PATCH 33/33] Adding license attribute --- package.json | 1 + 1 file changed, 1 insertion(+) diff --git a/package.json b/package.json index 7fabf16..80be1d8 100755 --- a/package.json +++ b/package.json @@ -2,6 +2,7 @@ "name": "docs.c9.io", "version": "0.1.70", "private": true, + "license": "CC-BY-NC-SA-3.0", "repository": { "type": "git", "url": "git://github.com/c9/docs.c9.io.git"