alexherbo2 has quit [Read error: Connection reset by peer]
alexherbo21 is now known as alexherbo2
alexherbo2 has quit [Ping timeout: 256 seconds]
alexherbo2 has joined #amber
FromGitter has quit [Ping timeout: 244 seconds]
FromGitter has joined #amber
<FromGitter>
<damianham> @eliasjpr @drujensen @andrewc910 RE: manually adding plugin shard to shard.yml etc. My plugin implementation does not require manually updating the ROOT/shard.yml. It downloads and installs the plugin (using shards in the background BTW) with 1 command. Maybe if you guys had given it a whirl....... :)
<FromGitter>
<drujensen> What do you mean by “in the background”? What happens when you want to upgrade it? Can you use shards update like all the other dependencies? How does that work exactly?
<FromGitter>
<drujensen> Let’s say there is a vulnerability in the auth plugin. Is there a way to update it easily? Same question for @andrewc910
<FromGitter>
<drujensen> wdyt if we create a shard.yml in the `/plugins` directory? treat them like submodules similar to maven’s submodules?
<FromGitter>
<drujensen> not sure if that will work or not, just throwing out ideas.
<FromGitter>
<drujensen> i think its important to have a way to control which version of the plugin is installed. It shouldn’t just copy it in without a way to manage the version. shards have version control built in with semantic versioning controls.
<FromGitter>
<drujensen> I should be able to easily update the version in the `shard.yml` and run `shard install` to update it.
<FromGitter>
<damianham> @drujensen those are good points. My plugin implementation does not support updating the plugin because the plugin install mechanism generates code rather than provide library services in **/lib**. I think @andrewc910 plugin PR is the same in that it is also a code generator. My implementation does what you are suggesting by creating a shard.yml for plugins in a sub folder so that concept does work, and it does
<FromGitter>
... so automatically with the amber plugin install {plugin_spec} command (this is what I meant by "in the background"). I think that we can come to a conclusion that supports proper installation and updating of plugin shards if we switch the plugins to be library services that are located in **/plugins** rather than cod ... [https://gitter.im/amberframework/amber?at=5f3ab97caecae32e8ecbe9af]
<aphorise>
Anyway I've been able to get it show in the right place but it doesnt function when I clock the button that otherwise works in another place.
<aphorise>
Let me try and push it to my local fok - easier to share like that.
<aphorise>
On branch 'ui_login_unwrap' - I'm basically trying to get Unwrap working that I've added to login page... the reset of the start instructions should be clear and its the first screen when it launches. https://github.com/aphorise/vault/tree/ui_login_unwrap/ui - it just should not actually post but rather behave the same as when you're signed in (under tools) - login token is 'root' btw
<aphorise>
I'm frustratingly close but I dont know enough how I should be mimicing the same some of behaviour without tranistion... so any help would be very much appreciated.
<aphorise>
$20 bonous on offer too :-)
<aphorise>
It's all the Rupees I have
<FromGitter>
<eliasjpr> Honestly I think we should iterate over it and ask for community feedback
<FromGitter>
<eliasjpr> @aphorise I’ll take a look
<FromGitter>
<eliasjpr> @aphorise this is a full javascript application, not a crystal one. Not sure if you were trying to refer to `ember.js` not `amber`
<FromGitter>
<juozasg> hey, i'm experimenting with amber framework. trying to make a frontend grpc services. is there anyplace to find amber crystal doc. i tried building them from source. it didn't work but i could be doing it wrong
<aphorise>
yes I'm sorry my mistake - thank you for take a look