heroku

Postgres error with Sinatra/Haml/DataMapper on Heroku

旧城冷巷雨未停 提交于 2020-02-06 05:10:27
问题 I'm trying to move a simple Sinatra app over to Heroku. Migration of the Ruby app code and existing MySQL database using Taps went smoothly, but I'm getting the following Postgres error: PostgresError - ERROR: operator does not exist: text = integer LINE 1: ...d_at", "post_id" FROM "comments" WHERE ("post_id" IN (4, 17,... ^ HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts. It's evident that the problem is related to a type mismatch in

Rails how to Gzip Javascript? (Heroku)

混江龙づ霸主 提交于 2020-02-04 07:34:25
问题 I have run google page speed and it is saying that I should Gzip my javascript files? How do I gzip my javascript files? My website is hosted on heroku if that mattter 回答1: This answer is out of date but I can't delete it because it was accepted. So I'm turning it into a community wiki so that people can fix it up. Heroku should be gzipping everything automatically (as long as the client supports it of course). From an old blog post: All apps deployed to Heroku automatically compress pages

Deploying Create-React-App with Rails API on Heroku

五迷三道 提交于 2020-02-04 05:52:25
问题 I'm having an issue getting my react /rails app to work on heroku. I've managed to get it deployed and the rails server starts but I'm not seeing my react app. I feel like I'm close but can't figure out what's missing. So my process is currently to run npm run build locally from the client directory which builds a 'build' directory in client. I then commit the results of the build and push to Heroku with git push heroku master . I then navigate to the heroku app in a browser where I'm only

Solution for background jobs on Heroku?

孤街醉人 提交于 2020-02-04 05:04:47
问题 I've used Delayed Job on Heroku's older stacks (Aspen and Bamboo), but with their new(ish) Cedar stack, I'd like to try something more efficient. The specific background jobs I'm performing are API calls to different carriers (UPS, FedEx, USPS, etc etc) and I typically am processing thousands every hour. I need to be able to process jobs concurrently to get through the queue quickly. On top of that, I'd like to try to reduce costs. On the previous stacks where I've been using Delayed Job, I

Solution for background jobs on Heroku?

拟墨画扇 提交于 2020-02-04 05:04:41
问题 I've used Delayed Job on Heroku's older stacks (Aspen and Bamboo), but with their new(ish) Cedar stack, I'd like to try something more efficient. The specific background jobs I'm performing are API calls to different carriers (UPS, FedEx, USPS, etc etc) and I typically am processing thousands every hour. I need to be able to process jobs concurrently to get through the queue quickly. On top of that, I'd like to try to reduce costs. On the previous stacks where I've been using Delayed Job, I

Checking in code without deploying on Heroku

我们两清 提交于 2020-02-03 09:32:29
问题 I've been successfully running an app on Heroku, but now would like to work with a collaborator on it. Is there a way with can check in (and pull) code without deploying it live? Right now a git push deploys to code the live site. 回答1: Create a new branch and use that. git checkout -b BRANCH_NAME git push heroku BRANCH_NAME 回答2: One of the advantages of git is that it is distributed and decentralized. You can have multiple remote repositories configured. I suggest you use github for

Checking in code without deploying on Heroku

拜拜、爱过 提交于 2020-02-03 09:30:51
问题 I've been successfully running an app on Heroku, but now would like to work with a collaborator on it. Is there a way with can check in (and pull) code without deploying it live? Right now a git push deploys to code the live site. 回答1: Create a new branch and use that. git checkout -b BRANCH_NAME git push heroku BRANCH_NAME 回答2: One of the advantages of git is that it is distributed and decentralized. You can have multiple remote repositories configured. I suggest you use github for

How to stop Firebase auth handled backend from carrying on to other browsers / sessions

ぐ巨炮叔叔 提交于 2020-02-02 17:45:26
问题 I'm in the process of creating an authentication based web app. It works fine when only one session is running, but if a user on another session is logged in, it carries through to all sessions allowing everyone to see that user's information and use their permissions. I've determined that this is because I handle all of my authentication backend from this post: Firebase Auth : User session carried to different browser But I'd like to know whether there are any fixes without having to handle

How to stop Firebase auth handled backend from carrying on to other browsers / sessions

喜欢而已 提交于 2020-02-02 17:45:18
问题 I'm in the process of creating an authentication based web app. It works fine when only one session is running, but if a user on another session is logged in, it carries through to all sessions allowing everyone to see that user's information and use their permissions. I've determined that this is because I handle all of my authentication backend from this post: Firebase Auth : User session carried to different browser But I'd like to know whether there are any fixes without having to handle

Node JS environment variables and Heroku deployment

Deadly 提交于 2020-02-02 08:32:31
问题 I have a project using the dotenv package to load my environment variables in my NodeJS application I use the following line var dotenv = require('dotenv').load({ silent: true }); //Example of use username: process.env.CONVERSATION_USERNAME I am now planning to deploy this application on Heroku. However, for some obvious security reasons i don't want to commit my .env file. I'm new to NodeJS and I would like to know if there is a way to say "If the .env file doesn't exists, load the