MARKDOWN SOURCE
# Product: ino VPS server ## Problem Today, I can build an app image with ino, but getting that app onto my VPS and controlling it remotely takes a separate workflow. I want ino to let me deploy and manage my VPS apps from the same tool I already use to build them. I want to use the once abstractions for doing so. ## Success metric A routine app update reaches a healthy state on the VPS within 2 minutes of starting the ino deploy command, measured end to end on a representative app and VPS. ## Announcement — the blog post before the feature ino can now take an app from your local build to your own VPS. Build as usual, then choose to send the image to your server and bring the app up remotely. You can also connect your own tools to ino to manage the apps running there. Your server stays yours, while ino makes the path from build to running app feel like one workflow. The ino server runs on the VPS as managment layer. ## Screens No UI — the experience is through the http API
Product: ino VPS server
Problem
Today, I can build an app image with ino, but getting that app onto my VPS and controlling it remotely takes a separate workflow. I want ino to let me deploy and manage my VPS apps from the same tool I already use to build them. I want to use the once abstractions for doing so.
Success metric
A routine app update reaches a healthy state on the VPS within 2 minutes of starting the ino deploy command, measured end to end on a representative app and VPS.
Announcement — the blog post before the feature
ino can now take an app from your local build to your own VPS. Build as usual, then choose to send the image to your server and bring the app up remotely. You can also connect your own tools to ino to manage the apps running there. Your server stays yours, while ino makes the path from build to running app feel like one workflow. The ino server runs on the VPS as managment layer.
Screens
No UI — the experience is through the http API