marketing
openvscode-server
marketing | openvscode-server | |
---|---|---|
9 | 125 | |
- | 4,726 | |
- | 1.4% | |
- | 0.0 | |
- | 6 days ago | |
TypeScript | ||
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
marketing
-
Gitlab AI is going head to head with GitHub Copilot
GitLab team member here. Thanks for flagging.
Our web team is working to resolve this issue here: https://gitlab.com/gitlab-com/marketing/digital-experience/b...
-
The Future of the Gitlab Web IDE
> Having a web-based IDE is great for newcomers and will work on cheap Chromebooks or iPads
Good call, thanks. GitLab team member here.
From my experience as GitLab trainer in my past job, a web frontend to edit files hides the complexity of Git on the CLI, and helps with the "5 min success" to get going and learning. This can help with team member onboarding, as well as OSS projects looking for contributors.
Combined with CI/CD pipeline feedback in the same interface, without context switches, it makes the learning story easier to follow too.
The first workshops to get started with GitLab CI/CD from 2 years ago, are linked in the documentation, and use the Web IDE. [0] Seen great learning curves from the wider community :-) Taking a note to create a new workshop with the new IDE in the future. [1]
[0] https://docs.gitlab.com/ee/ci/quick_start/
[1] https://gitlab.com/gitlab-com/marketing/corporate_marketing/...
- Gitlab Handbook's HN Page
-
Let's make faster Gitlab CI/CD pipelines – From 14 to 3 mins
Thank you for the great thoughts :)
> And maybe only cache the downloads on the main branch.
$CI_COMMIT_REF_SLUG resolves into the branch when executed in a pipeline. Using it as value for the cache key, Git branches (and related MRs) use different caches. It can be one way to avoid collision but requires more storage with multiple caches. https://docs.gitlab.com/ee/ci/variables/predefined_variables...
In general, I agree, the more caches and parallel execution you add, the more complex and error prone it can get. Simulating a pipeline with runtime requirements like network & caches needs its own "staging" env for developing pipelines. That's a scenario not many have, or might be willing to assign resources onto. Static simulation where you predict the building blocks from the yaml config, is something GitLab's pipeline authoring team is working on in https://gitlab.com/groups/gitlab-org/-/epics/6498
And it is also a matter of insights and observability - the critical path in the pipeline has a long max duration, where do you start analysing and how do you prevent this scenario from happening again. Monitoring with the GitLb CI Pipeline Exporter for Prometheus is great, another way of looking into CI/CD pipelines can be tracing.
CI/CD Tracing with OpenTelemetry is discussed in https://gitlab.com/gitlab-org/gitlab/-/issues/338943 to learn about user experiences, and define the next steps. Imho a very hot topic, seeing more awareness for metrics and traces from everyone. Like, seeing the full trace for pipeline from start to end with different spans inside, and learning that the container image pull takes a long time. That can be the entry point into deeper analysis.
Another idea is to make app instrumentation easier for developers, providing tips for e.g. adding /metrics as an http endpoint using Prometheus and OpenTelemetry client libraries. That way you not only see the CI/CD infrastructure & pipelines, but also user side application performance monitoring and beyond in distributed environments. I'm collecting ideas for blog posts in https://gitlab.com/gitlab-com/marketing/corporate_marketing/...
For someone starting with pipeline efficiency tasks, I'd recommend setting a goal - like shown in the blog post X minutes down to Y - and then start with analysing to get an idea about the blocking parts. Evaluate and test solutions for each part, e.g. a terraform apply might depend on AWS APIs, whereas a Docker pull could be switched to use the Dependency proxy in GitLab for caching.
Each environment has different requirements - collect helpful resources from howtos, blog posts, docs, HN threads, etc. and also ask the community about their experience. https://forum.gitlab.com/ is a good spot too. Recommend to create an example project highlighting the pipeline, and allowing everyone to fork, analyse, add suggestions.
-
Gitlab has 15 ad trackers, 22 3rd party cookies, and a keylogger
Good morning HN. I am the DRI (directly responsible individual) for about.gitlab.com and I have created this issue to audit our trackers, cookies, and other data collection on the marketing website https://gitlab.com/gitlab-com/marketing/inbound-marketing/ma...
Our product does not include the tracking that is used on the marketing site.
- Join Q1 2021 Gitlab Hackathon for Wider Community
-
We are building a better Heroku
Hi,
> This was not a poor accident by a single employee. It's noble that the author tries to take all the blame on himself, but honestly, I feel like that is a moment where a leader has to step in and accept their mistake and not let a small trooper eat all the bullets.
The issues you have found are all assigned to me, or I created them. My task is to create blog posts, some of which being a hackathon and challenge. The KPI are impressions, other metrics are hard to measure. As a Developer Evangelist, I often need to learn new technologies, or dive into unknown areas connecting the dots.
You can learn more about our focus areas in our handbook: https://about.gitlab.com/handbook/marketing/community-relati...
I'm focussing on the Ops side, with a backend development background in the past 15 years. I was once a maintainer of an OSS monitoring project called Icinga, a Nagios fork back then. I decided to take on a new journey with becoming a Developer Evangelist in March 2020 (you can learn more on my website https://dnsmichi.at/about/ in case you're interested).
That being said, I've found it interesting to learn about web apps and their deployment, and dive into new things. Never having found a use case for trying Heroku, March brought up one: There was a Twitter theme of "Everyone is building a better Heroku" - https://twitter.com/adamhjk/status/1369704730218299392?s=27
From there, I thought of learning Heroku while comparing it with the 5 minute production app. I underestimated the challenge of creating a web app with a persistent backend, and decided to stick with the simple battleships demo I had initially found.
This state of the blog post felt good enough for me, and I did not include the persistent backend just yet, but moved it into a separate blog post. This is feedback I got during the review.
Turns out that this decision was wrong, next to other negative raw sentiments I had added in the blog post.
You can try to convince that it is not my fault, and I will convince you - it is, and I am standing up for it. Public and transparent.
I know we all get better from making mistakes. The lesson I learned today helped me improve a talk I gave at a meetup in my evening, it added technical insights as well as helped with the story line. That's the tracking issue: https://gitlab.com/gitlab-com/marketing/corporate_marketing/...
We will continue to iterate, and have a retrospective on what we can improve from the lessons learned today. Thanks for your feedback.
- A Free and Open Alternative to GitHub Sponsors
openvscode-server
-
Reviving decade-old Macs with antiX and MX Linux (2022)
> Yeah, sadly there are entry level laptops cheaper than a phone or said monitor plus a keyboard and mouse
Many people already have a monitor, mouse, and keyboard lying around. They'll also have a phone already. Plus, there are very cheap docks where you can just slide your phone into a laptop shell, priced similarly to the worst and most awful Chromebooks imaginable.
> So nothing works offline.
You can run a vscode server on your phone (https://github.com/gitpod-io/openvscode-server/releases). What's lacking is the VSCode GUI, so pointing a browser at http://[::1]:8080/ will work just fine.
- [Self Hosted] Alternative auto-hébergée aux codepaces
-
Building a remote/cloud dev box IDE specifically for digital nomads. What do you want?
This already exists!! https://www.gitpod.io/
-
Understanding the Networking Basics of Lambda to RDS Connectivity
The next part is the 'Public access' parameter which needs to be aligned with the DB Subnet Group configuration. When set to No, the provisioned ENI will only have Private IP. If you try to access it from the Internet, your PC or a cloud development environment such as Gitpod that would obviously not be accessible. However, if you set it to Yes, the ENI will also have a Public IP and a Public hostname (DNS endpoint). This settings can be changed without the need to re-provision the RDS which is quite handy.
-
Crazy coworker manages entire development environment in single docker container
https://www.gitpod.io/ does this
-
Self-hosted alternative to Codespaces? (With .devcontainer support)
Not sure what .devcontainer means, but you can take a look to https://github.com/gitpod-io/openvscode-server or https://github.com/coder/code-server
-
Does anyone have a solution to replace my laptop?
I am using this project (https://github.com/gitpod-io/openvscode-server/) to run on my Linux box, then I can access it's server through my web browser.
-
️Appwrite + Gitpod: One Click Setup
We look forward to integrating more with Gitpod in the future! Check out the Gitpod homepage for more information and new development environment templates.
-
[D] I recently quit my job to start a ML company. Would really appreciate feedback on what we're working on.
I suggest you check out https://www.gitpod.io, which does more general provisioning of GitOps clusters/Pods in their managed Kubernetes clusters. It's not specifically ML, but we've looked at it for POC ML projects that want basic hosting.
-
A second look at Amazon CodeCatalyst – CI/CD natively on AWS to empower developers to deliver faster and reduce heavy lifting
The last option - the Dev Environments - is the most exciting functionality - it gives you the possibility to host development environments (similar to Gitpod) on AWS using Cloud9 but also, and this is really cool, using Visual Studio or JetBrains IDEs. When using that option, the IDE on your local PC is only the "presentation layer", the source code is stored and run on an AWS instance and the IDE uses remote connectivity to talk to the Dev Environment in the background.
What are some alternatives?
languagetool - Style and Grammar Checker for 25+ Languages
Code-Server - VS Code in the browser
gitlab-runner
vscode-dev-containers - NOTE: Most of the contents of this repository have been migrated to the new devcontainers GitHub org (https://github.com/devcontainers). See https://github.com/devcontainers/template-starter and https://github.com/devcontainers/feature-starter for information on creating your own!
piku - The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.
openvsx - An open-source registry for VS Code extensions
www-gitlab-com
template-docker-compose - A Docker Compose template, configured for Gitpod (www.gitpod.io) to give you pre-built, ephemeral development environments in the cloud.
5-minute-production-app
gitpod - The developer platform for on-demand cloud development environments to create software faster and more securely.
LibreSelery - Continuous distribution of funding to your project contributors and dependencies. Integrated into GitHub Actions
vscodium - binary releases of VS Code without MS branding/telemetry/licensing