[foreman-dev] Re: assistance adding new models and migrations

[Andrew Schofield]

On this line: 

>> + add_index :katello_repository_dockers, [:docker_manifest_id, 
:repository_id], :unique => true

Add a :name => "my_new_index_name_thats_shorter_than_63_chars"


On Wednesday, November 2, 2016 at 9:56:10 PM UTC-4, Tom McKay wrote:
>
> Used the other cv filter migrations to try to make mine. I'm not sure how 
> to get around this, though:
>
> ArgumentError: Index name 
> 'index_katello_repository_dockers_on_docker_manifest_id_and_repository_id' 
> on table 'katello_repository_dockers' is too long; the limit is 63 
> characters 
>
> On Wed, Nov 2, 2016 at 7:40 PM, Tom McKay  > wrote:
>
>> In the spirt of "teach me to fish", can someone guide me on how best to 
>> add new entries to the database from some new models I need? I am adding 
>> content view filters that will limit docker tags[1]. Similar models already 
>> exist for rpm packages so I had a good place to start, but I'm struggling 
>> to know what the migrations should be.
>>
>> Thanks!
>>
>>
>> [1] 
>> https://github.com/Katello/katello/compare/patternfly-compliance...thomasmckay:docker-cv-filter
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[foreman-dev] assistance adding new models and migrations

[Tom McKay]

In the spirt of "teach me to fish", can someone guide me on how best to add
new entries to the database from some new models I need? I am adding
content view filters that will limit docker tags[1]. Similar models already
exist for rpm packages so I had a good place to start, but I'm struggling
to know what the migrations should be.

Thanks!


[1]
https://github.com/Katello/katello/compare/patternfly-compliance...thomasmckay:docker-cv-filter

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] Smart or Foreman Proxy? Let's do Foreman Smart Proxy

[Tomas Strachota]

On 10/17/2016 03:26 PM, Greg Sutcliffe wrote:

On 17 October 2016 at 14:12, Lukas Zapletal > wrote:


> This appears more inconsistent than the current situation, as there will
> now be three terms, differing between the UI names ("Foreman Smart
> Proxy"), API/module names ("smart proxy"), and package names ("foreman
> proxy").

That's indeed a very true statement, I'll add that the new term aims to
be the glue between the other two.


I think I agree with Dominic, a third standard to fix two other
standards is a common mistake.


To be honest, I'd rather kill "Smart Proxy" than "Foreman Proxy" if I
had to choose just one.


+1 to that, Foreman Proxy would be my choice.


+1 for Foreman Proxy



Greg

--
You received this message because you are subscribed to the Google
Groups "foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-dev+unsubscr...@googlegroups.com
.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.