On the memcachier faq page I see that the supported platform providers are Heroku, AppFog, AWS and a few others, but GitHub Pages is not mentioned explicitly. Furthermore, they say:
What does the memcachier gem do?
The memcachier gem is relevant for customers in Heroku, AppFog, and cloudControl. It copies the MEMCACHIER* environment variables to MEMCACHE*, which is where most client libraries expect to find SASL credentials.
So, in other words, the question is: does it make sense to use the memcachier and dalli gems on my Octopress blog, hosted on GitHub Pages?
GitHub pages runs a small subset of plugins / gems. memcachier and dalli gems are not on the list
Related
The project I'm working on currently deploys our private node packages via github packages. Our current workflow is for each developer to create and maintain their own personal access token, and then we use a central account's PAT for automation in AWS.
I was wondering if it's possible to authenticate with github packages without the use of Actions or PAT's?
As of 2022-07-30
No, it is not possible to use github packages without a personal access token (PAT):
It is not possible to upload without a PAT (which makes sense as it prevents random people to upload binaries to your package repo);
It is not possible to download without a PAT (not even publicly available packages can be used);
As early as 2019-10-20, people have requested github to remove PATs as a requirement for mainly downloading public packages.
The idea is that users of libraries should not need to have a github account to access a developer's package.
Sadly, the request for pat-less package downloads was not granted by Github to this day.
If you want a package registry without a hassle, it might be wise to look for other registries, such as MavenCentral or JitPack (not necessarily meant for node packages),
or host a service yourself.
I even had to link a cached webpage, as the original question has been removed from Github community along with a bunch of related questions.
Another question on github, stating pat-less access to packages is still on the roadmap for "fall 2021" is here.
I could not find what the current status of this feature is.
Edit: It is possible to download binaries without a PAT for public repositories using jitpack.io. Jitpack builds the given jar/aar on their servers.
You can add jitpack as a repository to your build system, and use the jitpack-specified URL to reference releases, branches, or specific commits.
Sadly, there is no way to refer to packages (yet).
However, this system allows your users to use your code without needing PATs nor a Github account.
I'd like to offer an alternative.
You may use a Gradle plugin of mine (magik, I was exactly in your shoes) to easier the consumption of artifacts from your Github Packages for Gradle clients.
It require you to save your read-only PAT on the repo itself, so that the users don't have to deal with any authentication (apart using the plugin above mentioned)
So, I just recently started using GitHub, and now I need to use someone else's code, so there are some things I want to know.
The principal two forms of using someone's code that I saw were by cloning their repository, and by installing it with npm. My doubts are:
Is there any difference in the usage of code between those two?
Can I do any of those things through the GitHub desktop? How?
If I install with npm do I still need to clone the repository?
After installing it do I still need to install it on my machine to use locally?
After installing or cloning it can I use it anywhere on my repo?
And last of all about the MIT License. From what I saw it grants pretty much free usage of the application, but do I need to make mention of its usage? And if yes, where would that appear?
i am interested in building a github app. reading through github Setting up your development environment to create a GitHub App documentation it explains that a github app is based on a http server which will handle webhooks.
yet, on every github app i installed, the app\installation did not require anything that involves hosting and/or creation of http server in order to deploy the app to my github accout.
for such github apps, which are installed directly through the github marketplace (you can take probot stale and rennovate as examples for such apps)
where do these application run? (e.g.; does github deploys the app on a dedicate (virtual) server?).
what are the resources limitations for such apps (amount of memory, cpu, etc.?)
how can the github app logs be accessed by the github account owner who installed such app?
links for reference and an answer will be great.
GitHub App is just another app that you create. GitHub apps are treated as first-class citizens when it comes to integrating with GitHub. One can use Nodejs , Ruby, etc to build the App. Once the app is ready it can be hosted on a Server just like any other server hosted apps. You register your app on GitHub by providing relevant details.
So, coming to your questions.
The Apps can run on any hosting service of your choice. It can be a Windows Server, Heroku, etc.
I believe it is only limited by the resource of your server or the hosting service provider that you chose. However you might be ineterset in erading more about the Rate Limit More on Rate limits here.
GitHub app logs are something which only the developer will be able to see. To the end user ,i.e. the repo owner who installed the GitHUb app on his repos, all that will be available are the checks , statuses and any other details that the developer of app decided to display.
A very handy guide on Deployment and other details : Probot Documentation. This documentation is great if you are planning to use the probot framework for developing your github apps, but most of the instructions still stand true in case you decide to pick up a different tech stack.
The most important thing to realise about a (so-called?) Github App is that the App itself does not run anywhere - or at least that is what I would argue. Basically Github Apps are two linked mechanisms, both a bit of infrastructure. The first of these mechanisms is access control, essentially replacing use of user PATs - you can give relatively fine grained access to repos that the App is installed in, rather than just giving access to all repos the user can access. The second mechanism is that of webhooks - generating events as requested.
What Github Apps do not directly provide is the bit between this - handling the webhooks and generating API calls using the App for access. Basically you are on your own and need to do it yourself. The plus, #asif-kamran-malick mentioned, is that you have freedom to implement it how you see fit.
One alternative possibility is that the App itself, rather than setting to handle ongoing Webhooks, runs on installation and looks to add Actions into the repo. Never done it, but some of the github examples seem to work this way. Of course, Actions are run within Github environments and are potentially subject to resource limits. Apart from this though, Actions are a completely separate "beast" and should not be confused.
I want to host a simple blog on Github pages. Therefore I set up a repository and used Hexo as a compile and deployment tool.
After testing my site locally I run the following command:
hexo deploy --generate
Sadly I, just a few seconds later, get the following message from Github:
The page build failed with the following error:
The hacker theme is not currently supported on GitHub Pages. For more
information, see
https://help.github.com/articles/adding-a-jekyll-theme-to-your-github-pages-site.
For information on troubleshooting Jekyll see:
https://help.github.com/articles/troubleshooting-jekyll-builds
If you have any questions you can contact us by replying to this
email.
How can I publish my site using the hacker theme? If this is not possible which themes are supported by Github? How do I use them with Hexo?
Bypassing Jekyll on GitHub Pages
It is now possible to completely bypass Jekyll processing on GitHub
Pages by creating a file named .nojekyll in the root of your pages
repo and pushing it to GitHub. This should only be necessary if your
site uses files or directories that start with underscores since
Jekyll considers these to be special resources and does not copy them
to the final site.
Source: https://github.com/blog/572-bypassing-jekyll-on-github-pages
[..] I used the username.github.io repo and deployed directly to master
and it works!
https://github.com/CodeDaraW/Hacker/issues/9
For educational purpose, I am writing a server instance in GCE(google compute engine) to serve a few web apps mostly (to be) written in Dart and Polymer.
My workflow is, when my students log-in the server above, they will automatically fork those web apps into their own registries in their own server instances for further development.
My issues are,
How to serve web applications(they are git registries as well) in GCE like Github Pages?
Is it possible to manipulate Github Pages to serve web apps mostly using Dart and Polymer packages?
Thanks in advance.
I found out answers to my questions.
1. How to serve web applications(they are git registries as well) in GCE like Github Pages?
Use CI(continuous integration).
2. Is it possible to manipulate Github Pages to serve web apps mostly using Dart and Polymer packages?
No.
My question is summarized to the sentence that 'Is it possible to assign IP addresses on index.html files in git repositories?'. If possible, there is no need of CI processes at all as 'A repository itself is A web server or directory running the code'.
CI is more or less documented in Github Pages and Gitlab CI etc. Though details are different, they commonly use hooks(or webhooks) to notify something from repo to another server(s), which are application servers.
In my opinion, GIT is NOT designed and has NOT evolved for web applications, but for 'REAL' applications needing compile/build processes. So, there is no mechanism to run a repo as a web server. So, the only solution is to hack the source code of Gitlab etc. to make a better Github Pages(it supports only static pages, and NOT JS and other libraries etc.).
Disclouse: based on the advice of Günter Zöchbauer