Comments

• 

  almost 5 years ago by okurz | Reply

  Hm, sounds interesting. I wonder in general, how does this simplify deployment? Isn't an automatic update of RPM very easy or what is the current approach used?

  • 

    almost 5 years ago by cschum | Reply

    RPMs are not a natural way to package Rails applications. Containers work better there. And with Kubernetes you also get the necessary configuration of the infrastructure around the application.

    Even simpler would be to use a PaaS system. But as an exercise to learn how to do it with Kubernetes this is an interesting project.

  ×
  Edit Comment 3158
  # A First Level Header
  ## A Second Level Header
  
  Use one asterisk to *emphasize*
  
  Use two asterisks for **strong emphasis**
  
  * Use asterisks
  * for lists
  
  This is an [example link](http://example.com/)
  
  This is an ![example image](http://paste.opensuse.org/view/raw/68957446)
  
  This is a user link @hans
  
  This is a project link hw#some-cool-title
  
  More Complex Markdown Help
  Formatting Help
  • Edit
  • Preview
  RPMs are not a natural way to package Rails applications. Containers work better there. And with Kubernetes you also get the necessary configuration of the infrastructure around the application. Even simpler would be to use a PaaS system. But as an exercise to learn how to do it with Kubernetes this is an interesting project.
   
  ×
  Reply to cschum
  RPMs are not a natural way to package Rails applications. Containers work better there. And with Kubernetes you also get the necessary configuration of the infrastructure around the application.
  Even simpler would be to use a PaaS system. But as an exercise to learn how to do it with Kubernetes this is an interesting project.
  ---
  # A First Level Header
  ## A Second Level Header
  
  Use one asterisk to *emphasize*
  
  Use two asterisks for **strong emphasis**
  
  * Use asterisks
  * for lists
  
  This is an [example link](http://example.com/)
  
  This is an ![example image](http://paste.opensuse.org/view/raw/68957446)
  
  This is a user link @hans
  
  This is a project link hw#some-cool-title
  
  More Complex Markdown Help
  Formatting Help
  • Edit
  • Preview
   
×
Edit Comment 3132
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Hm, sounds interesting. I wonder in general, how does this simplify deployment? Isn't an automatic update of RPM very easy or what *is* the current approach used?
 
×
Reply to okurz
Hm, sounds interesting. I wonder in general, how does this simplify deployment? Isn't an automatic update of RPM very easy or what is the current approach used?
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  almost 5 years ago by kiall | Reply

  Re the .gitlab-ci.yml you gave - you could also use the new GitLab Kubernetes integration with CaaSP. This can do some cool stuff, like review apps (Deploy a full instance of the stack for each PR, destroying it again when closed or merged)... Check the products "Operations -> Kubernetes" section at the side to add connection details for your cluster.

×
Edit Comment 3188
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Re the .gitlab-ci.yml you gave - you could also use the new GitLab Kubernetes integration with CaaSP. This can do some cool stuff, like review apps (Deploy a full instance of the stack for each PR, destroying it again when closed or merged)... Check the products "Operations -> Kubernetes" section at the side to add connection details for your cluster.
 
×
Reply to kiall
Re the .gitlab-ci.yml you gave - you could also use the new GitLab Kubernetes integration with CaaSP. This can do some cool stuff, like review apps (Deploy a full instance of the stack for each PR, destroying it again when closed or merged)... Check the products "Operations -> Kubernetes" section at the side to add connection details for your cluster.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview