Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/zztkm/heroku-buildpack-v

Heroku-compatible buildpack for V - vlang.io
https://github.com/zztkm/heroku-buildpack-v

buildpack heroku heroku-deployment vlang

Last synced: 3 months ago
JSON representation

Heroku-compatible buildpack for V - vlang.io

Host: GitHub
URL: https://github.com/zztkm/heroku-buildpack-v
Owner: zztkm
License: mit
Fork: true (litenite42/heroku-buildpack-v)
Created: 2021-07-16T10:46:09.000Z (over 3 years ago)
Default Branch: master
Last Pushed: 2022-04-22T01:58:38.000Z (over 2 years ago)
Last Synced: 2024-05-03T08:32:03.744Z (6 months ago)
Topics: buildpack, heroku, heroku-deployment, vlang
Language: Shell
Homepage:
Size: 56.6 KB
Stars: 2
Watchers: 0
Forks: 1
Open Issues: 1
Metadata Files:
- Readme: README.md
- License: LICENSE

Awesome Lists containing this project

awesome-v - Heroku Buildpack for V - Deploy V apps on Heroku. (Applications / Web)

README

# Heroku Buildpack for V
![](images/vlogo.png)

This buildpack installs the most recent commit of V from [https://github.com/vlang/v](https://github.com/vlang/v).

This repo is forked from https://github.com/louis77/heroku-buildpack-v

## Installation

### Create a Heroku app with this buildpack

```sh
$ heroku create --buildpack https://github.com/zztkm/heroku-buildpack-v.git
```

### Set the buildpack for an existing Heroku app

```sh
$ heroku buildpacks:set https://github.com/zztkm/heroku-buildpack-v.git
```

## Getting started

To deploy a V app, your repo should contain at minimum these files:

```shell
app.v
vpm.txt
```

`app.v` will be compiled and run on deploy.

`vpm.txt`is a list of VPM modules that will be installed using `v install ...` before your app is compiled. List one module per line and *terminate with a new line*:

```
nedpals.jsonrpc
nedpals.args
```

You can omit `vpm.txt`, no packages will be installed then.

Find available VPM modules in the [VPM modules directory](https://vlang.io/modules).

`remote.txt` is a list of remote git repo urls and their module name that will be installed using `git clone remote_url ~/repo_author_name/module_name` and `ln -s ~/repo_author_name ~/.vmodules/` before your app is compiled. List one repo and module name per line separated by a space and *terminate with a new line*:

```
https://www.github.com/username/repo_name.git repo_author_name module_name
https://some_other_url/username/another_repo.git repo_author_name module_name_too
```

creates the following directories:
```
~/.vmodules/repo_author_name/module_name
~/.vmodules/repo_author_name/module_name_too
```

You can omit `remote.txt`, no repos will be cloned then.

### Procfile

If there is no Procfile in the base directory of the code being built, then a default Procfile is created that that looks like this:

```
web: ./app
```

## Hacking on this buildpack

To change this buildpack, fork it on GitHub & push changes to your fork. Contributions are very welcome!

## TODO

- [ ] Support to define desired commit/branch of V
- [ ] Cache compiled V binary
- [ ] Cache installed modules
- [ ] Add config facility

## Credits