Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
sfba.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for the San Francisco Bay Area. Come on in and join us!

Administered by:

Server stats:

2.4K
active users

sfba.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

#circleci

1 post1 participant0 posts today
C.W. Smith<p><a href="https://social.mechanizedarmadillo.com/tags/Drupal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Drupal</span></a><br><a href="https://social.mechanizedarmadillo.com/tags/DDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DDev</span></a><br><a href="https://social.mechanizedarmadillo.com/tags/Storage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Storage</span></a></p><p>So I have been thinking of ways to make my DDev projects more mobile for me at minimum. I would prefer a workflow that allowed me to work on them, send to <a href="https://social.mechanizedarmadillo.com/tags/Codeberg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Codeberg</span></a> or <a href="https://social.mechanizedarmadillo.com/tags/Github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Github</span></a>, maybe run through <a href="https://social.mechanizedarmadillo.com/tags/CircleCI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CircleCI</span></a> or something similar, then load to the Ubuntu based servers my sites are on.</p><p>I am gonna at least start moving projects to USB stick. They can be moved more easily that way and not be dependent on the internet for transfer.</p><p>Any recommendations from people who actually know what they are doing are welcome. Cause I am just a novice.</p>
Esparta :ruby:<p>[cont] about bundle being killed after upgrading <a href="https://ruby.social/tags/ruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ruby</span></a> 3.4.x</p><p>So why it worked on my coworker's machine and <a href="https://ruby.social/tags/GItHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GItHub</span></a> actions but didn't work on <a href="https://ruby.social/tags/CircleCI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CircleCI</span></a> or within a container with <a href="https://ruby.social/tags/Docker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Docker</span></a> or <span class="h-card" translate="no"><a href="https://fosstodon.org/@Podman_io" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>Podman_io</span></a></span>? the answer is right in the Gemfile.lock!</p><p>bundle tries to do their work relying on what's on Gemfile.lock, since it's kind-of a recipe to have a reliable ruby bundle. Sadly, it's not a perfect system, some decisions taken may affect the outcome.</p><p>4/5</p>
ExploreLive feeds
About