I want to code directly on production with VSCode, make some changes, and commit them (for fast prototyping, not a live server). I'm testing responses from external services, so I need a publicly-accessible URL.
Is that possible with heroku?
When I SSH intro Heroku from a terminal, I can't git commit cause I get fatal: not a git repository
Also, running heroku ps:exec on VSCode remote extension pack doesn't work.
No, this is not possible on Heroku without some very awkward hoop-jumping. Heroku is a platform-as-a-service provider, not a remote workstation.
I'm testing responses from external services, so I need a publicly-accessible URL
Your best bet may be to use something like ngrok or localtunnel.
These tools let you temporarily route traffic from a publicly-accessible address to your local development environment. At a high level, it looks something like this:
Start your development server locally
Start ngrok or localtunnel locally
Take the publicly-accessible URL the tool gives you and tell the external service to use it
Related
My organization blocks ngrok, so every time I run the Shopify serve command, it fails with a connection error.
So is there any way to just start the Shopify local server? that way I can use cloudfared to tunnel the local server to a subdomain.
When I search on google I found no answer to this question.
I had success running the server without the ngrok.
Here are my steps:
Prepare a cloud server, install Nginx.
config domain settings, and forward the request to your local port.
If you are using a router, only router has a public IP, so you need to forward the request to your pc. You could config it in the router.
then you need to update .env file, update host value
Go partner.shopify.com, app settings. put your URL to the whitelist.
use npm run dev to start your project.
I also set HTTPS in nginx. Due to ngrok server is far away from my location. so after using this way. the starting time is much faster.
Start the server by
npm run dev
instead of,
shopify app serve
I have a local repository on my pc, and did this with Tortoisegit.
I also have an Amazon Web Services EC2 instance running Windows Server 2012, and have also installed Tortoisegit on there. I have opened port 9418(TCP), and created inbound firewall rules for it. I have a domain pointing to the server, and the server is accessible via HTTP (running apache) at my domain.
I have created a folder c:\Repos on the SERVER, and have set the HOME environment variable to point to this. Inside Repos I created a new folder named ProjectX.git, and then using the tortoise shell right click, created a BARE repository at the new folder.
I want to do an initial PUSH of my local repo, to the one on my server, by adding the server as a remote, but I'm not sure I have the url right.
// also for clarification who is user?
// Do I use the windows username?
git://user#hostname/ProjectX.git
Please refrain from 'elitist' answers such as 'use CLI idiot' or 'why dont u take the time to learn git properly instead of using gui shortcuts', which I see all over git questions online. GUI is there for a reason, enough said.
Decided that there just simply isn't enough good documentation out there to get the git:// protocol setup on windows, and to permanently share repos, i opted for SCM Manager. Which happens to work great. Very easy setup.
I'm trying to deploy a MEAN stack app on Google Cloud platform using their functionality "click-to-deploy". Once my VM is created, I can ssh to it, clone my git repository and run my server. My app is accessible at the given IP address on the right port. Everything works fine until I end my session which automatically stops my server. How can I make sure node will still be running afterwards ?
A better way to do it would have been to use the command forever start
I've looked all over and can't figure out if you could use Cherokee instead of Apache or Nginx for gitlab. I'd rather not run multiple webservers (and imagine that they could conflict anyway). I'm giving this a shot on Ubuntu Server 12.10.
For the record, I've already installed gitlab with this guide up to the Nginx section (with all default settings other than passwords, email addresses, and hostname). I'd like to install gitlab at git.mydomain.com and I would prefer for the local server files to be located at /var/www/git.mydomain.com, as I keep all of my domains under /var/www/.
Since you already have all of the Ruby config done, you just need to hook cherokee
up for hosting RoR by following this guide http://cherokee-project.com/doc/cookbook_ror.html
My only problem turned out to be an issue with Ruby. Once that was resolved, I set up gitlab to use a port (though sockets should work too). Everything seems to work pretty well, except for an issue with pushing over HTTPS, but that might have something to do with my local Eclipse/eGit install.
So yes, gitlab will work with Cherokee.
It's really difficult to explain. But basically, I have an amazon instance, and I want to ssh into it and run a local server on it with sinatra. so I would ssh into the amazon instance, git clone my repo, and run ruby config.ru. Then I want someone else to be able to see that exact local server that is being ran. One of the things I've done is added a security group, port 4567 HTTP so that I can access it via public dns. It works on a rack app but it doesn't work on the sinatra, I've even tried a 'hello world' sample app to try to get it working.
I'm not sure if there is a specific reason that you want to do this from an Amazon server or not, but if you just want someone else to see your sinatra app, you could simply use localtunnel.
Using this, you can simply run localhost on your OWN computer, then run localtunnel PORTNUMBER and it will give you a URL that your app will now be visible from. You can then give that URL to anyone you want.
Example of use:
$ ruby myapp.rb
$ localtunnel 4567
A URL will then be displayed for you to copy-paste to a friend. Easy as that.
I use this a lot when developing web apps to be mobile friendly and want to quickly look at the app on my phone without having to deploy to a server.