Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file lib/afterlife. To experiment with that code, run bin/console for an interactive prompt.
TODO: Delete this and the text abovxe, and describe your gem
bin/install in the repository rootconfig.yml on ~/.afterlife/config.yml based on the AWS credentials found on mifiel's bitwarden vaultRun afterlife help for a list of all available commands
Logs can be found on ~/.afterlife/logs/cdn.log
Running afterlife cdn start will run the CDN web server in the background. Running in foreground using afterlife cdn start --foreground will display errors and content normally found in logs in console instead.
After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and the created tag, and push the .gem file to rubygems.org.
Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/afterlife.
FAQs
Unknown package
We found that afterlife demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.