1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
|
%global _empty_manifest_terminate_build 0
Name: python-colony
Version: 1.4.6
Release: 1
Summary: Colony Framework
License: Apache License, Version 2.0
URL: http://getcolony.com
Source0: https://mirrors.aliyun.com/pypi/web/packages/14/53/ed8c578cbf1d3842d60c8411a86cc1e81e49422e3feedbd232ab3473c0e5/colony-1.4.6.tar.gz
BuildArch: noarch
Requires: python3-appier
%description
# [](http://getcolony.com)
The Colony Framework is an open source plugin framework specification. Implementations of the specification offer a runtime component model, that allows for plugins to be installed, started, stopped, updated and uninstalled without requiring the application container to be stopped. The specification relies heavily on the Inversion of control principle, in order to make it easier for application components to discover and interact with each other.
Colony aims to eliminate the complexity typically associated with the creation of modular applications, through a simplified unified model for component development. Practical applications can range from modular enterprise software to application mashing.
## Quick start
### Handicraft
* Install Colony using `pip install colony`
* Run the command `RUN_MODE=devel colony`
### Virtualenv
* Start and activate the environment using `virtualenv venv && source venv/bin/activate`
* Install Colony in the system using `pip install colony`
* Deploy the console package using `cpm install console_interface`
* Run your new colony using the command `RUN_MODE=devel colony`
### Docker
* Create a new directory to serve as base for the build `mkdir colony && cd colony`
* Retrieve the `Dockerfile` from the repo using `wget https://github.com/hivesolutions/colony/raw/master/assets/docker/Dockerfile`
* Create the new docker image using `docker build --tag self/colony .`
* Execute colony with `docker run -e RUN_MODE=devel -i -t self/colony`
To actually do something useful look into [How to Establish your Colony in 3 Easy Steps](http://getcolony.com/docs/colony/documentation_how_to_establish_your_colony_in_3_easy_steps.html)
## Installation
### For development
* Set `PYTHONPATH` to the `colony/src` path so that the Python source files may be included
* Set `PATH` to the `colony/scripts/pypi` to used the provided base scripts
### For production
## Usage
Most of the colony operation are run through the `cpm` command:
* `cpm clone <target>` - clones the base colony instance into the target directory (new project)
* `cpm cleanup <target>` - cleans the current instance removing extra files
* `cpm pack <target>` - packs the current instance into a .zip file
* `cpm generate [target] <...>` - generates a .json descriptor file for the provided Python file and then runs
the build operation for the generated .json file, effectively build the package item
* `cpm build [descriptor] <...>` - builds the target .json descriptor file into a package file
* `cpm deploy [package]` - deploys the target .cbx file into the current instance
* `cpm info [package]` - prints information about the package to the standard output
* `cpm install [name] <...>` - installs the package with the provided name from the remote repositories
* `cpm upgrade` - updates the complete set of packages deployed in the instance
* `cpm require [path] <...>` - installs the complete set of packages defined in the requirements file
* `cpm upload [target] <repo>` - generates a package for the provided path and then uploads it to the currently
configured primary repository, or another repository if defined
## Testing
In order to run the complete set of available tests for the deployment use either `colony test`
or `MODE=test colony` and Colony Manager will boot directly to unit testing and exit in error in
case at least one test fails.
## Features
* Runtime modularity.
* No restart required for deploying new plugins, updating or reconfiguring existing ones.
* Simplified component model (easy to create a plugin, even easier to combine existing ones).
* Capabilities: simple extension points which allow your plugins to take advantage of future plugins which adhere to the capability API.
* Dependencies: simplified dependency management, just declare the id of the plugin your plugin needs in order to function and the plugin manager will ensure your plugin only gets loaded when the conditions are met.
* Most importantly, runs [Colony Plugins](https://github.com/hivesolutions/colony_plugins).
And remember this is just the base runtime, to understand the kind of things you can do with Colony, browse the [Colony Plugins repository](https://github.com/hivesolutions/colony_plugins).
## Contributing
Although Colony is still in an early stage we're welcoming help for all kinds of work.
The best ways to get involved:
1. Join the [mailing list](http://groups.google.com/group/colony-users).
2. Send pull requests for bug fixes or new features and improvements.
3. Help make the [docs](http://getcolony.com/docs/colony/) better.
## Extensions
To find Python native extension required for some of the plugins used the following sites:
* Python Imaging Library (PIL) [link](https://pillow.readthedocs.io/).
* Reportlab PDF Generator [link](http://www.reportlab.com/).
* Unofficial Windows Binaries for Python Extension Packages [link](http://www.lfd.uci.edu/~gohlke/pythonlibs/).
* MySQL driver for Python [link](http://sourceforge.net/projects/mysql-python/).
## Project information
* Colony Base Source: https://github.com/hivesolutions/colony
* Colony Base Plugins Source: https://github.com/hivesolutions/colony_plugins
* Web: http://getcolony.com
* Docs: http://getcolony.com/docs/colony/
* Mailing list: http://groups.google.com/group/colony-users
* Twitter: http://twitter.com/colonyframework
## License
Colony is an open-source project currently licensed under the [Apache License, Version 2.0](http://www.apache.org/licenses/).
## Build Automation
[](https://travis-ci.com/github/hivesolutions/colony)
[](https://github.com/hivesolutions/colony/actions)
[](https://coveralls.io/r/hivesolutions/colony?branch=master)
[](https://pypi.python.org/pypi/colony)
[](https://www.apache.org/licenses/)
%package -n python3-colony
Summary: Colony Framework
Provides: python-colony
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-colony
# [](http://getcolony.com)
The Colony Framework is an open source plugin framework specification. Implementations of the specification offer a runtime component model, that allows for plugins to be installed, started, stopped, updated and uninstalled without requiring the application container to be stopped. The specification relies heavily on the Inversion of control principle, in order to make it easier for application components to discover and interact with each other.
Colony aims to eliminate the complexity typically associated with the creation of modular applications, through a simplified unified model for component development. Practical applications can range from modular enterprise software to application mashing.
## Quick start
### Handicraft
* Install Colony using `pip install colony`
* Run the command `RUN_MODE=devel colony`
### Virtualenv
* Start and activate the environment using `virtualenv venv && source venv/bin/activate`
* Install Colony in the system using `pip install colony`
* Deploy the console package using `cpm install console_interface`
* Run your new colony using the command `RUN_MODE=devel colony`
### Docker
* Create a new directory to serve as base for the build `mkdir colony && cd colony`
* Retrieve the `Dockerfile` from the repo using `wget https://github.com/hivesolutions/colony/raw/master/assets/docker/Dockerfile`
* Create the new docker image using `docker build --tag self/colony .`
* Execute colony with `docker run -e RUN_MODE=devel -i -t self/colony`
To actually do something useful look into [How to Establish your Colony in 3 Easy Steps](http://getcolony.com/docs/colony/documentation_how_to_establish_your_colony_in_3_easy_steps.html)
## Installation
### For development
* Set `PYTHONPATH` to the `colony/src` path so that the Python source files may be included
* Set `PATH` to the `colony/scripts/pypi` to used the provided base scripts
### For production
## Usage
Most of the colony operation are run through the `cpm` command:
* `cpm clone <target>` - clones the base colony instance into the target directory (new project)
* `cpm cleanup <target>` - cleans the current instance removing extra files
* `cpm pack <target>` - packs the current instance into a .zip file
* `cpm generate [target] <...>` - generates a .json descriptor file for the provided Python file and then runs
the build operation for the generated .json file, effectively build the package item
* `cpm build [descriptor] <...>` - builds the target .json descriptor file into a package file
* `cpm deploy [package]` - deploys the target .cbx file into the current instance
* `cpm info [package]` - prints information about the package to the standard output
* `cpm install [name] <...>` - installs the package with the provided name from the remote repositories
* `cpm upgrade` - updates the complete set of packages deployed in the instance
* `cpm require [path] <...>` - installs the complete set of packages defined in the requirements file
* `cpm upload [target] <repo>` - generates a package for the provided path and then uploads it to the currently
configured primary repository, or another repository if defined
## Testing
In order to run the complete set of available tests for the deployment use either `colony test`
or `MODE=test colony` and Colony Manager will boot directly to unit testing and exit in error in
case at least one test fails.
## Features
* Runtime modularity.
* No restart required for deploying new plugins, updating or reconfiguring existing ones.
* Simplified component model (easy to create a plugin, even easier to combine existing ones).
* Capabilities: simple extension points which allow your plugins to take advantage of future plugins which adhere to the capability API.
* Dependencies: simplified dependency management, just declare the id of the plugin your plugin needs in order to function and the plugin manager will ensure your plugin only gets loaded when the conditions are met.
* Most importantly, runs [Colony Plugins](https://github.com/hivesolutions/colony_plugins).
And remember this is just the base runtime, to understand the kind of things you can do with Colony, browse the [Colony Plugins repository](https://github.com/hivesolutions/colony_plugins).
## Contributing
Although Colony is still in an early stage we're welcoming help for all kinds of work.
The best ways to get involved:
1. Join the [mailing list](http://groups.google.com/group/colony-users).
2. Send pull requests for bug fixes or new features and improvements.
3. Help make the [docs](http://getcolony.com/docs/colony/) better.
## Extensions
To find Python native extension required for some of the plugins used the following sites:
* Python Imaging Library (PIL) [link](https://pillow.readthedocs.io/).
* Reportlab PDF Generator [link](http://www.reportlab.com/).
* Unofficial Windows Binaries for Python Extension Packages [link](http://www.lfd.uci.edu/~gohlke/pythonlibs/).
* MySQL driver for Python [link](http://sourceforge.net/projects/mysql-python/).
## Project information
* Colony Base Source: https://github.com/hivesolutions/colony
* Colony Base Plugins Source: https://github.com/hivesolutions/colony_plugins
* Web: http://getcolony.com
* Docs: http://getcolony.com/docs/colony/
* Mailing list: http://groups.google.com/group/colony-users
* Twitter: http://twitter.com/colonyframework
## License
Colony is an open-source project currently licensed under the [Apache License, Version 2.0](http://www.apache.org/licenses/).
## Build Automation
[](https://travis-ci.com/github/hivesolutions/colony)
[](https://github.com/hivesolutions/colony/actions)
[](https://coveralls.io/r/hivesolutions/colony?branch=master)
[](https://pypi.python.org/pypi/colony)
[](https://www.apache.org/licenses/)
%package help
Summary: Development documents and examples for colony
Provides: python3-colony-doc
%description help
# [](http://getcolony.com)
The Colony Framework is an open source plugin framework specification. Implementations of the specification offer a runtime component model, that allows for plugins to be installed, started, stopped, updated and uninstalled without requiring the application container to be stopped. The specification relies heavily on the Inversion of control principle, in order to make it easier for application components to discover and interact with each other.
Colony aims to eliminate the complexity typically associated with the creation of modular applications, through a simplified unified model for component development. Practical applications can range from modular enterprise software to application mashing.
## Quick start
### Handicraft
* Install Colony using `pip install colony`
* Run the command `RUN_MODE=devel colony`
### Virtualenv
* Start and activate the environment using `virtualenv venv && source venv/bin/activate`
* Install Colony in the system using `pip install colony`
* Deploy the console package using `cpm install console_interface`
* Run your new colony using the command `RUN_MODE=devel colony`
### Docker
* Create a new directory to serve as base for the build `mkdir colony && cd colony`
* Retrieve the `Dockerfile` from the repo using `wget https://github.com/hivesolutions/colony/raw/master/assets/docker/Dockerfile`
* Create the new docker image using `docker build --tag self/colony .`
* Execute colony with `docker run -e RUN_MODE=devel -i -t self/colony`
To actually do something useful look into [How to Establish your Colony in 3 Easy Steps](http://getcolony.com/docs/colony/documentation_how_to_establish_your_colony_in_3_easy_steps.html)
## Installation
### For development
* Set `PYTHONPATH` to the `colony/src` path so that the Python source files may be included
* Set `PATH` to the `colony/scripts/pypi` to used the provided base scripts
### For production
## Usage
Most of the colony operation are run through the `cpm` command:
* `cpm clone <target>` - clones the base colony instance into the target directory (new project)
* `cpm cleanup <target>` - cleans the current instance removing extra files
* `cpm pack <target>` - packs the current instance into a .zip file
* `cpm generate [target] <...>` - generates a .json descriptor file for the provided Python file and then runs
the build operation for the generated .json file, effectively build the package item
* `cpm build [descriptor] <...>` - builds the target .json descriptor file into a package file
* `cpm deploy [package]` - deploys the target .cbx file into the current instance
* `cpm info [package]` - prints information about the package to the standard output
* `cpm install [name] <...>` - installs the package with the provided name from the remote repositories
* `cpm upgrade` - updates the complete set of packages deployed in the instance
* `cpm require [path] <...>` - installs the complete set of packages defined in the requirements file
* `cpm upload [target] <repo>` - generates a package for the provided path and then uploads it to the currently
configured primary repository, or another repository if defined
## Testing
In order to run the complete set of available tests for the deployment use either `colony test`
or `MODE=test colony` and Colony Manager will boot directly to unit testing and exit in error in
case at least one test fails.
## Features
* Runtime modularity.
* No restart required for deploying new plugins, updating or reconfiguring existing ones.
* Simplified component model (easy to create a plugin, even easier to combine existing ones).
* Capabilities: simple extension points which allow your plugins to take advantage of future plugins which adhere to the capability API.
* Dependencies: simplified dependency management, just declare the id of the plugin your plugin needs in order to function and the plugin manager will ensure your plugin only gets loaded when the conditions are met.
* Most importantly, runs [Colony Plugins](https://github.com/hivesolutions/colony_plugins).
And remember this is just the base runtime, to understand the kind of things you can do with Colony, browse the [Colony Plugins repository](https://github.com/hivesolutions/colony_plugins).
## Contributing
Although Colony is still in an early stage we're welcoming help for all kinds of work.
The best ways to get involved:
1. Join the [mailing list](http://groups.google.com/group/colony-users).
2. Send pull requests for bug fixes or new features and improvements.
3. Help make the [docs](http://getcolony.com/docs/colony/) better.
## Extensions
To find Python native extension required for some of the plugins used the following sites:
* Python Imaging Library (PIL) [link](https://pillow.readthedocs.io/).
* Reportlab PDF Generator [link](http://www.reportlab.com/).
* Unofficial Windows Binaries for Python Extension Packages [link](http://www.lfd.uci.edu/~gohlke/pythonlibs/).
* MySQL driver for Python [link](http://sourceforge.net/projects/mysql-python/).
## Project information
* Colony Base Source: https://github.com/hivesolutions/colony
* Colony Base Plugins Source: https://github.com/hivesolutions/colony_plugins
* Web: http://getcolony.com
* Docs: http://getcolony.com/docs/colony/
* Mailing list: http://groups.google.com/group/colony-users
* Twitter: http://twitter.com/colonyframework
## License
Colony is an open-source project currently licensed under the [Apache License, Version 2.0](http://www.apache.org/licenses/).
## Build Automation
[](https://travis-ci.com/github/hivesolutions/colony)
[](https://github.com/hivesolutions/colony/actions)
[](https://coveralls.io/r/hivesolutions/colony?branch=master)
[](https://pypi.python.org/pypi/colony)
[](https://www.apache.org/licenses/)
%prep
%autosetup -n colony-1.4.6
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "\"/%h/%f.gz\"\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-colony -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Thu Jun 08 2023 Python_Bot <Python_Bot@openeuler.org> - 1.4.6-1
- Package Spec generated
|
