aptible / support Goto Github PK

For Intercom/Olark, plus Mixpanel/Google Analytics.

"Disk node" RabbitMQ in the database layer?

See aptible/dashboard.aptible.com#287

There appears to be a bug in node#0.12.2/npm#2.75 that causes npm install to fail on git/ssh installed packages.

Pinning node to 0.12.1 and npm to 2.7.3 fixes this issue.

This has been observed on a couple occasions. Opening this bug issue as a placeholder for a future fix or documentation.

Is there any way to have all logs, across deploys, going into the same system?

@samyount w/ @sandersonet and @fancyremarker

• Currently, all "Contact Us" links fall back to mailto: links. Should these be a contact form? (Maybe fine as-is.)
• "Fenced" code currently overflows its div, needs scrollbar. #1 below

Using this ticket as a placeholder for mobile design issues. Feel free to create checklists here.

Any articles referencing Dashboard UI or features should be checked for accuracy before fully launching Diesel.

Add icons and update data/quickstart.yml for:

• Meteor

e.g.

http://snag.gy/BLCcX.jpg

For example, in Slack, our links look like:

Not that Slack is canonical, but it uses Twitter cards, Open Graph, and oEmbed. Could we use frontmatter to write something like <meta property="og:description" content="Short description here" /> and any other relevant info?

• Notifications
• Invoices
• Credit cards

Not just across containers in the same release, but across releases over time.

Despite adding a hack to update the mtime of all files on git clone, running ADD . still always busts the cache. This is because we chose to update the mtime to the time of the last commit — so if any new commits came in, it would bust the cache. This is true of any deploy, and so our hack would only work for operations like aptible rebuild.

This hack uses a fixed time for the mtime, and I figure we should do the same.

@jbergknoff — do you see any issues with a fixed mtime?

cc: @fancyremarker

When running a large data migration on our Rails app we received a cascade of postgreSQL related errors when running migrations in the after_release context as defined in .aptible.yml:

1. PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly,
2. PG::ConnectionBad: PQsocket() can't get socket descriptor: ROLLBACK * 2,
3. PG::ConnectionBad: PQsocket() can't get socket descriptor,
4. ActiveRecord::StatementInvalid: PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly,
5. NoMethodError: undefined method 'result_error_field' for nil:NilClass (related to Rails' postgres adapter)

The migration run failed in the same way twice. The migration was successful when ran manually via aptible ssh rake db:migrate.

This would allow things like local asset precompilation to be performed in a before_release step.

Pending the added feature of writing an app's current ENV to .aptible.env in the project directory, we should update this documentation.

This article can summarize and link to other specific uses.

What are our options for searching a static site?

Off the top of my head:

• lunr.js is used by GitHub Docs
• SwiftType is used by EmberJS Docs

Attempts to deploy to Aptible are failing with the following error:

Writing objects: 99% (130/131)
Writing objects: 100% (131/131)
Writing objects: 100% (131/131), 17.08 KiB | 0 bytes/s, done.
Total 131 (delta 92), reused 42 (delta 18)
remote: (8ミ | INFO: Authorizing...
remote: (8ミ | INFO: Initiating deploy...
remote: (8ミ | INFO: Deploying...
remote: INFO -- : Building app image from source...
remote: ERROR -- : Archive::Tar::Minitar::FileNameTooLong
remote: (8ミ | FATAL: Deploy failed.

"Account" should be used to refer to user and organizational accounts. "Stack" "Environment" is preferred when referring to a VPC or deployment environment.

For some reason, Swiftype is failing to crawl the domain, even after adding a permissive /robots.txt :

For example, "Quickstart" is a poor choice for searchability. Instead I think we should use "Getting started with.." as this is probably closer to what an actual user would search.

@sandersonet: my thinking here is we should deploy to both staging and production on each successful merge to master. I don't see many situations where we wouldn't want to automatically update the live support site when we've got new content. We can always deploy manually to staging to preview what a given PR will look like before merging it.

Thoughts?

Reference @Fluidbyte's config here: https://gist.github.com/Fluidbyte/3ff968db14dda5cc770a

Search inputs just sit blankly when no results match and don't respond to Enter/submit.

Right now, the only way to create a remote SSH session is via aptible ssh, which creates a new, one-time use container from your app's current configuration and image. For security reasons, this does not have access to your live app's process space.

In the future, we may support running commands against live app containers, a la docker exec, but that's not being contemplated currently. Leaving this issue open to address any related questions.

The most popular search term in Swiftype is deploy--the results of which aren't very helpful for newcomers. We should write an article that summarizes how deployment works and links out to the quickstart guides. We should manually pin this to the top of the deploy query.

Sign up/in at https://aptible.zendesk.com/hc/en-us/requests. You can also request permission to view all of your organization's tickets, by sending us a note.

By adding a subject field, we can use SwiftType to search for support articles that match the support subject.

Most of these are already written, just keeping track of a total list here which we can check off from when merged.

Migrating to Aptible

• How do I migrate from Heroku?
• How do I import my existing Heroku PostgreSQL database?
• How do I import my existing MongoDB database?
• How do I import my existing MySQL database?

HIPAA

• What is Protected Health Information (ePHI)?
• What is a Business Associate Agreement (BAA)?
• What third-party SaaS companies will sign a BAA?
• What constitutes a breach of ePHI?
• What should I do if I believe a breach of ePHI has occurred?

Using the PaaS

• What databases does Aptible support?
• How do I add a background worker to my app?
• How do I set up Travis CI to deploy to Aptible?
• How do I set up Circle CI to deploy to Aptible?
• How do I scale my app?
• What is a "container" on Aptible?
• How do I set up Papertrail for my Aptible apps?
• How do I automate database migrations for my app?
• How do I update the SSL certificate and private key for my app?
• How do I add a new external domain to my app?
• How should I store static assets when using Aptible?
• How do I prevent public internet access to my app?
• My app requires a specific OS package. How should I install it?
• How do I run scheduled tasks (cron jobs) on Aptible?
• How do I contribute to Aptible's open source repos?
• How do I access environment variables inside a Dockerfile?
• What is the difference between the CMD in my Dockerfile and the processes in my Procfile?
• How do I set up caching for Bundler?
• How do I set up caching for npm packages?
• How do I restore from an Aptible database backup?

Aptible CLI

• How do I install the Aptible CLI?
• How do I connect to my Aptible database using a GUI tool?
• How do I connect to my Aptible database from outside Aptible?
• How do I view my app logs?
• How do I set environment variables for my app?
• How do I SSH into my app?
• How do I restart my app?
• How should I configure sensitive variables for my app?

Troubleshooting

• My deploy failed. What should I do?
• How do I fix the error "no pg_hba.conf entry for host, ... SSL off"?
• When I push to Aptible, Git says "Everything up-to-date." What should I do?
• My deploy failed, saying "before_release commands failed." What should I do?
• My deploy failed, saying "Container failed to start." What should I do?
• My deploy failed, saying "Health check failed." What should I do?
• My deploy failed, saying "No Procfile found." What should I do?
• My app stopped working. What should I do?
• I just added a domain to my app and it's not responding. What should I do?
• My deploys take too long. How can I speed them up?
• My app is processing requests slowly. What should I do?

Your Aptible Account

• How do I invite a new user to Aptible?
• What different plans does Aptible offer?
• How do I set up a separate staging environment for my apps and databases?

Specifically, this could either mean us being able to create feature branches on the fly with staging data on aptible, or potentially have a way to push staging data from aptible directly to heroku would be great!

So for feature branches, this might look like...
aptible pg:copy $STAGING_APP_NAME::DATABASE_URL DATABASE_URL --app $APP_NAME --confirm $APP_NAME

How can I determine when each step of my deploy occurred?

We should do this only when we have our own quay.io/aptible/buildstep image.