On 23.05.2017 21:08, Josh Berkus wrote:
> On 05/23/2017 07:25 AM, Martin Pitt wrote:
>> This is now sufficiently useful and robust for getting some wider feedback 
>> and
>> testing. For easier and faster development it's currently a standalone
>> project/repository [4], it includes a README how to install it:
>>
>>     mkdir -p ~/.local/share/cockpit
>>     cd ~/.local/share/cockpit
>>     git clone https://github.com/martinpitt/cockpit-os-updates.git
>>     npm install
>>     npm run compile
>>
>> If you don't have "npm", you need to install it first with "sudo yum install 
>> npm".
> 
> This brings up an idea: it would really really help with user testing if
> we could build test versions like this one (maybe from PRs) into
> containers and make them available with a tag.
> 
> It's pretty trivial for me, or other users, to install an alternate
> version of Cockpit via container. Running npm compile (even inside a
> container) is kind of a pain.
> 
> I'll give building this one as a cockpit/ws container a shot.

Yeah, that would be cool.

Let us know (here on the list) when you do end up building such a
container (I imagine with systemd, NetworkManager, and friends inside it).

If it's not too hacky, we could have our bots do this automatically for
each Cockpit pull request.

Cheers,

Stef

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
cockpit-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to