So, I've download the Heroku Integration, with PyCharm 2.7.2. I've put in the API key, added an app with a name I chose. I want to create just a basic django app on a heroku free account. So, what do I do now? Could someone please give me some basic instructions as to how you get started with actually uploading all the stuff in your project to Heroku?
Not sure about the pycharm integration, but the easy answer is git push to heroku.
When using pycharm, I just do Menu >> VCS >> Git >> Push. Then if heroku is not your default remote (origin), check the box for push to alternate remote/branch. I choose heroku and master and away it goes!
Related
I have three different apps I have set up on heroku. When I run the apps, the apps show up in the browser, but they are very old versions of the apps.
I have configured each project to deploy a new build everytime changes are pushed to the linked github repos, and the activity feed claims the builds are successful. The logs also don't appear to show any errors.
I also know heroku is receiving the pushes because it is running new builds when I push and when I monitor the "see diff", the changes are displayed.
I am at a total loss as to what is going on and it's very frustrating. If nothing else, does anyone have any suggestions for similar services to heroku that do not have so many deploy issues?
Try and make sure heroku has the latest, from a local GitHub repo clone:
cd /path/to/my/local/clone
git remote add heroku /url/heroku/repo
git push --force heroku HEAD:master
That will make sure there is no "detached HEAD" situation on the heroku side, which would explain why the push does not update the working tree.
I have a Parse application that will soon be used in production, and I need to be able to continue developing things locally without breaking things for live users when I make changes to cloud code.
I have cloned the app, and can now deploy to either the production or staging app using the parse deploy staging and parse deploy production commands, however these commands only work if I am on the master branch.
What I would like to have are two branches in git, one that can be pushed to my staging app, and the other that can be pushed to the production app.
At the moment all I can think of doing is to just tag commits in master as being pushed to production, then continue ontop of that for development, but that is going to be a nightmare if I need to patch the released app when I have all my development changes on master.
Pushing directly to the heroku git repos doesn't seem to work either, parse deploy must be doing something extra (plus it tries to build the app so I can see when things go wrong).
Another issue is that when other developers start working on this as well, we won't be able to all deploy to the development server, and as far as I know there isn't an easy way to run parse cloud code locally on windows.
What is the best way to manage all this?
You have to setup parse-server (use parse-server-example), parse-dashboard and mongoDB on a local or remote development server. You and your team can now develop everything locally, test and then deploy to production.
I am creating a very small and clean meteor app and have recently updated to v0.9 of meteor to be able to get rid of meteorite as "package manager".
For me it is really important in a way not to have any deployment specific stuff wired up into the sourcecode if it is possible.
What I am trying to do in a way is to have a good and clean Continuous Integration running. Right now I am using Codeship to run the tests and then push to heroku. But since I updated top meteor v0.9 there not seems to be a working buildpack.
Is it a reasonable way to create a buildpack on my own? That one would not have to do more than just install node, npm and meteor. Or is there another way to have the app bundled on a "build server" (can codeship do that?) and then have it somehow pushed to heroku as normal node.js app with all the necessities and dependencies?
Concerning the buildpack way:
I have been trying to install meteor via
curl https://install.meteor.com | /bin/sh
But when I run
meteor deploy --directory deploy
I get
bundle: You're not in a Meteor project directory.
This buildpack (which I authored) works for meteor >0.9 using meteor's native packager; no meteorite:
https://github.com/AdmitHub/meteor-buildpack-horse
You could start off with the existing buildpack (or one of the many forks of it).
It should be relatively easy without meteorite since you would no longer have to worry about it, its just getting rid of meteorite and updating the version of node. https://github.com/oortcloud/heroku-buildpack-meteorite
Regarding deploying to heroku. meteor deploy is meant to deploy to *.meteor.com or via Meteor's upcoming commercial product. Deploying to heroku is also relatively easy.
Deploying to heroku is setting up the buildpack, adding the git remote and git pushing to it. Also easy, perhaps easier, than meteor deploy.
During the git push process heroku will take your meteor app, bundle it, download node and run it (as in the buildpack). It's quite easy that way. One nice thing without meteorite is I imagine the build process is much faster.
How to deploy a web application to heroku in new version of cloud9 ?
The previous version had the deploy button, but cannot be found in new version
In the new version of Cloud9 we don't have support for deployment from the UI yet unfortunately, but we're going to add those features soon. In the meantime, we recommend using the command line from the built-in terminal, as described on our documentation site here: https://docs.c9.io/deploying_via_cli.html
In addition to the directions that Ivar published above you may need some additional steps.
For Rails deployment you need to:
1) Add your SSH key via the command line to heroku using: $ heroku keys:add
Source: https://devcenter.heroku.com/articles/keys
2) Remove SQLite and add Postgresql
Directions and source: https://devcenter.heroku.com/articles/sqlite3
I noticed this too but I have already setup my deployment using snap-ci.com it takes about a minute and when you check into your repository snap-ci will deploy it to heroku for you. I know it doesn't exactly answer your question but its a very simple alternative. I would add that down the road if you need additional deployment steps you are already part way there if you use a CI system.
I managed to do it via c9 command line as there were some proxy issues which I couldn't figure out in my local computer.
How do I modify the source of an installed package in Heroku? It's a django app, but I suppose it shouldn't make much of a difference?
Heroku uses Git to manage your source code. Please see the quickstart guide at https://devcenter.heroku.com/articles/quickstart.
You will have to install Heroku Toolbelt, which is a command-line tool. With that application, you will be able to manage and deploy your heroku application.
If you ment 3rd-party addons, I think these are submodules, so you may not be able to modify them.