This post is made by a Cycle employee highlighting a commonly asked question. It's being placed here for visibility, questions, feedback, feature requests, and general discussion.

If you're moving a project from Docker Compose to a Cycle Stack File, converting from one format to the other is a process worth automating.

Users can now visit the Docker Compose Converter from the Toolbox section of the website and they can easily paste in a docker compose file and get a cycle.json file out.

If you've used this tool we'd love to hear about your experience in the replies or creating a new thread with feedback, questions, or a request for new functionality!

How should I structure a deployment for multiple services inside a monorepo?

I've hit an error creating a stack and I wanted to find the build log for a stack image but Im not seeing it.

I just noticed something with the community site. When I log out of the Cycle portal, it doesn't log me out of the community site. I have to log out manually from the community site.

However, if I log out of the community site, it logs me out of the Cycle portal.

Sometimes I have to log in to different Cycle accounts depending on the project I'm working on, so I almost posted as someone else on the community site by accident even though I logged into my main account on the portal.

My team and I recently ran into an issue with curl where it would randomly error out with "host not found" when trying to ping a specific URL.

Here is how the Cycle team described it to me:

"it's a race condition that exists within that version of curl where it doesn't know what to do when it gets a "no ip found" for ipv6"

While this has been fixed in newer versions, those aren't available on our version of Debian.

As a workaround, we've added a custom DNS resolution record for that URL in the Discovery service in Cycle.

I hope this helps anyone else facing the same issue! Thank you to the Cycle team for your help with this.

Hi There,

We want to deploy the latest update to production. But.. there are some RSA pair keys that we need to have when the release deployed to production. The RSA key files are not pushed into git repository for security reason.

So.. the idea is, we need those key pair to be available in our production server everytime we deploy the latest update into production. How we can do that? Similar like ENV variables, but this time the value is "file"

Chris and Jake have been invaluable to us on countless occasions answering questions and getting to the bottom of any concerns of ours along the deployment process. Props to them and Cycle for top-tier support!

I have a cluster with two servers that are roughly in the same region. I have my production environment set up in such a way that all of the service containers (i.e., load balancer, discovery, and VPN) are located on one server and the main application containers are located on the other.

The "Neighbor Latency" panel says the latency between the servers is 8 ms.

With that being said, would it be better to have the service containers on the same server? Is there a standard practice for where the service containers should be deployed?

Any advice or insight would be appreciated!

How can I upload a profile picture to the community forum?

It is difficult to find the correct container when the number of containers in an environment reaches a certain point. Pagination is implement but you have to sift through page numbers to find the container you need.

Is there a chance to implement a search bar that will allow us to search for specific containers?

Is it possible to enable ipv4 (a.k.a. legacy mode networking) after the environment has been created?

It's quite hard to edit pipelines in the UI once you've got it in use (and thus rely on the ID staying the same, etc). Being able to move steps around would allow me to add new types of steps through the UI rather than having to use the API / manually reorder some JSON.

Hey all,

The selection bar containing each cluster and its environments uses, I think, time created to sort the cluster's environments. This is a bit of a hassle to scan, especially for folks who aren't necessarily deep in the Cycle ecosystem and are just trying to find their specific thing. Any for an alpha sort? I personally don't care if it's an option or the new default but maybe there's loyal created-at adherents as well.

It's pretty common for me to prototype setting up a new stack in a environment and we just spin things up containers and services through the UI as I test ideas and new PoCs. Then at some point I get to where we would like to rubber stamp a env structure into a staging, QA and then a Prod environment from that early prototyping.

--

• It would be nice if we could export a environment into a repeatable configuration.
• It would also be nice if we could export selected services into a configuration we can just paste into another environments configuration.

Wondering how to setup VPC Peering into one of my environments, specifically want to use for RDS. Trying to keep infra as locked down as possible and don’t want RDS instances exposed public internet.

I am having trouble understanding the docs related to Discovery setup and deployment with a mix of HA and Manual.

The docs say:

"High Availability - mark the discovery service for high availability, Cycle will attempt to create 3 instances of discovery spread between the available infrastructure based on geographic distance and provider."

https://docs.cycle.io/reference/environments/services/discovery/#managing-discovery

--

If I manually deploy to a dedicated server for Discovery type services. Will the HA flag also deploy 2 other nodes for me or does the manual deployment over ride the HA?

I'd love to be able to migrate environments. Im currently using stacks which gets me most of the way there. Is there a better way planned or other functionality coming?

I'd love to be able to embed video into a Thread.

The v1 load balancer is currently still in beta, as I've been using this for several months I was just wondering when it might be losing the beta tag.