I have created backend with perfectswift. Now I am trying to deploy that with heroku but I am getting some kind of error while pushing. Help me to solve this issue.
Seems to be an issue related with stack compatibility. You need to downgrade your stack:
heroku stack:set heroku-16 -a Your_App_Name
Stack Version Base Technology
----------------------------------------
Cedar-14 (deprecated) Ubuntu 14.04
Heroku-16 Ubuntu 16.04
Heroku-18 (default) Ubuntu 18.04
If you got that warning, means you'll need to use Cedar-14:
heroku stack:set cedar-14 -a Your_App_Name
List of Heroku's stacks:
https://devcenter.heroku.com/articles/stack
Related
I need to install Mosquitto 2.0 on my centOS linux machine.
The command available is yum install mosquitto works well, but it installs 1.6 version
I cannot use docker due to some limitation in my machine container eligibility.
Can anyone help me in this?
After some trial and error along with performing this is the best document I got so far.
https://www.disk91.com/2016/technology/internet-of-things-technology/install-mosquitto-mqtt-server-on-centos-to-publish-iot-data/
I have a legacy project that I'm trying to modernize, and part of that involves setting up a more efficient system of automated backups using mysqldump.
The app's database is using MySQL 5.6, and is hosted via an RDS instance. To get mysqldump up and running, I believe I need to install a version of mysql-client that corresponds to 5.6.
However, running apt-get install mysql-client installs 8.0 by default. However, I can't find any version-specific versions of mysql-client available. Running sudo apt-get install mysql-client-5.7 returns a notice that there's no installation candidate available.
Is it still possible to install older versions of mysql-client? If not, is there another way to get ahold of the mysqldump functionality?
Edit: As #exussum noted below, 8.0 is backwards compatible with 5.6 and 5.7. I was hitting errors when running mysqldump, which I'd assumed indicated incompatibility, but were actually related to my app specifically.
They are backwards compatible, so you can use mysql-client 8 to dump mysql-server 5.5
to get a specific version docker is great
(sudo apt install docker) to install
docker run mysql:5.6 mysqldump
will run mysqldump though docker, and you can choose your version there easily enough
My environment is using the following docker images:
postgres:11
dpage/pgadmin4
On a machine using unRaid for it's OS.
My issue is that I'm unable to backup anything on my postgres 11 server via pgadmin4. pgadmin4 returns the following error:
pg_dump: server version: 11.2 (Debian 11.2-1.pgdg90+1); pg_dump version: 10.5
pg_dump: aborting because of server version mismatch
There was a similar question asked here: PostgresSQL / pgAdmin4 / dump server version mismatch
They resolved in by changing the bin path, however these are docker images, and I am unable to find standalone binary file for Postgres 11 for Linux.
There is a issue in relation to this exact problem, but it was rejected and closed: https://redmine.postgresql.org/issues/3843
I'm looking for any assistance to get/replace the tools in pgadmin4 so it can properly talk to postgres11.
Turns out the solution for now is to use the snapshot build of pgadmin4's docker image.
It had something to do the tools available in Alpine Linux's docker image at the time, according to Dave Page, the maintainer of pgadmin4's docker images. They were updated recently and used in the snapshot image's build.
Whoever packaged the pgAdmin 4 you are using packaged it with a PostgreSQL v10 client.
So that's where you'll have to complain.
In this case it is obviously Dave Page.
The website of the Docker image (https://hub.docker.com/r/dpage/pgadmin4/) suggests:
Please report any issues through the pgAdmin support channels. See https://www.pgadmin.org/support/list/
So I guess the correct channel is to subscribe to that mailing list and voice your complaint there.
Sorry that this is so complicated, but the various tools in the PostgreSQL universe are maintained by different, albeit somewhat related, groups, each of which has its own channels.
I'm trying to deploy a Perfect app to Heroku, but I have only succeeded in getting the Swift compiler to run on Herolu with Perfect's own build pack. However, this build pack uses Swift 2.2 and my app runs on Swift 3.
I have then tried a variety of other build packs, including vapor, neonichu, and the seemingly most popular one: kylef.
But for everyone of them I get the same error message when pushing to Heroku:
Failed to detect set buildpack <url>.git
I feel I have exhausted my options, so this is my final try.
The makefile in your Heroku example project is referencing Ubuntu 14.0.4, the default Heroku app now is 16.0.4 as of May 2017. You need to set the ubuntu stack to cedar-14, and the swift app will deploy fine:
$ heroku stack:set cedar-14 -a example-app
$ git commit -m "update to cedar-14" --allow-empty
$ git push heroku master
I succeed with the error. The project structure didn't work.
Please use this project structure:
https://github.com/taplin/Perfect-Heroku-Buildpack-Example
I was linking this Buildpack at heroku:
https://github.com/PerfectlySoft/Perfect-Heroku-Buildpack
It worked fine for me. All other instructions you can take out of the video:
http://perfect.org/heroku-buildpack-for-perfect-and-swift.html
i have one server with redmine 1.2.1 and webrick webserver. In another new ubuntu server, i've just installed redmine 1.3.0 from the main repo, with apache+passenger. No problem with that.
Then i pg_dumped my old 1.2.1 database and put into my new postgresql for my 1.3.0 redmine. Everything works well except one thing. when i go to watch one of my repos (url like http://myhost.com/projects/myproject/repository/revisions/11806) I get this error
ActionView::TemplateError (PGError: ERROR: relation "changeset_parents" does not exist
This means that i didnt upgrade correctly my redmine, is there a way to upgrade this database in my new ubuntu server?
Thanks a lot.
Did you run the Redmine Database migration script?
rake db:migrate RAILS_ENV=production
This will need to be run as a root user in from the /usr/share/redmine directory or whereever you have installed Redmine to.